[Bug sanitizer/78028] ASAN doesn't find memory leak

2017-07-07 Thread barto at cambridgesemantics dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78028 David Barto changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug sanitizer/78028] ASAN doesn't find memory leak

2017-07-07 Thread tetra2005 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78028 Yuri Gribov changed: What|Removed |Added CC||tetra2005 at gmail dot com --- Comment #5

[Bug sanitizer/78028] ASAN doesn't find memory leak

2016-10-19 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78028 --- Comment #4 from Jakub Jelinek --- That wouldn't be WONTFIX, but FIXED, the support of GCC release branches mean that the bug is just fixed on the release branch and later on will make it into some newer minor release, we can't fix released ve

[Bug sanitizer/78028] ASAN doesn't find memory leak

2016-10-19 Thread barto at cambridgesemantics dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78028 --- Comment #3 from David Barto --- If it is restricted to 5.2, then we can close this as "won't fix"

[Bug sanitizer/78028] ASAN doesn't find memory leak

2016-10-19 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78028 --- Comment #2 from Jakub Jelinek --- I can't reproduce it with g++ 5.3.1 nor current trunk either.

[Bug sanitizer/78028] ASAN doesn't find memory leak

2016-10-18 Thread kcc at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78028 --- Comment #1 from Kostya Serebryany --- interestingly, this works for me with clang