This is the mail archive of the
mailing list for the GCC project.
Re: Newest gcc memory leak on gdb (heads up, only)
- From: law at redhat dot com
- To: Andreas Schwab <schwab at suse dot de>
- Cc: "Donn Terry" <donnte at microsoft dot com>, gcc at gcc dot gnu dot org
- Date: Thu, 30 May 2002 10:47:13 -0600
- Subject: Re: Newest gcc memory leak on gdb (heads up, only)
- Reply-to: law at redhat dot com
In message <email@example.com>, Andreas Schwab writes:
> "Donn Terry" <firstname.lastname@example.org> writes:
> |> Just in case someone else is also looking at this....
> |> Sometime between 5/13 and yesterday (5/28) evening (4:30P Pacific), a
> |> change was made to
> |> either gdb or gcc such that attempting to compile gdb/p-typeprint.c
> |> causes a bad memory leak (at least for me). (After 30 seconds it was at
> |> 300M
> |> and finally it grows enough to crash.)
> I'm seeing a similar leak when bootstrapping on ia64 with Ada enabled.
> The stage1 compiler is dying while compiling ada/exp_ch11.adb. The
> problem started yesterday, the last working CVS was from Tue May 28
> 08:06:25 UTC 2002.
The regression tester is also coughing.
I recommend we first get the regression tester back into a known good
state, then look and see if the "memory leak" problems are still around.
Right now the regression tester is failing to build mips-elf in a way that
could be related to my changes from yesterday. Clearly I'm in the process
of trying to build mips-elf myself so that I can investigate. :-)