This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/66339] g++ 5.1.0 Generates memory leak
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 19 Sep 2016 09:36:28 +0000
- Subject: [Bug libstdc++/66339] g++ 5.1.0 Generates memory leak
- Auto-submitted: auto-generated
- References: <bug-66339-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66339
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This behaviour is by design and is not a bug. Valgrind no longer shows the
allocation as reachable. Other tools might still show the memory as unfreed,
but it's still not a bug.