--- Comment #4 from pinskia at gcc dot gnu dot org 2006-08-15 18:22 ---
No feedback in 3 months.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from pcarlini at suse dot de 2006-05-15 16:46 ---
Missing a self-contained, simple testcase, certainly we cannot even imagine
debugging this... Also, please use valgrind, very reliable and commonly
available.
--
pcarlini at suse dot de changed:
What|Rem
--- Comment #2 from nanjiang dot shu at gmail dot com 2006-05-15 15:50
---
Subject: Re: memory leak with libstdc++ set
I have compiled the problem with gcc4.1.0, which was builded under
linux-pc-i686 from tar balls. The program exited with similar error
message. But I did not debuge
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-05-15 15:35 ---
Can you try a newer GCC since 3.3.x (and 3.4.x) are no longer being updated.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27615
