This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/68704] Memory leak in const char*
- 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: Fri, 04 Dec 2015 17:24:08 +0000
- Subject: [Bug c++/68704] Memory leak in const char*
- Auto-submitted: auto-generated
- References: <bug-68704-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68704
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That's not a memory leak, because the memory is still reachable (and still in
use).
It has nothing to do with const char* either, you'll see the same with an empty
main function. It's a memory pool used by the implementation to be able to
throw exceptions after malloc fails.