------- Comment #3 from fgiasson1 at yahoo dot ca 2009-03-05 18:04 -------
Andrew,
Thanks for your answer.
I did the test you suggested and there is no leak associated to it, so I
believe this pretty much sorts out the possibility that a bug in libc leads to
the leak. Moreover, as I said in the bug description, the problem is not
present when using libstdc++ 6.0.3, but is present when using libstdc++ 6.0.9
or 6.0.10.
This is not a Valgrind but, running the testcase I provided definitively shows
a growing memory usage.
Thanks in advance for your time
--
fgiasson1 at yahoo dot ca changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39366
