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.
