This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Mainline does not bootstrap for more than a week (Re: Newestgcc memory leak on gdb (heads up, only))
- From: Andreas Schwab <schwab at suse dot de>
- To: law at redhat dot com
- Cc: "Donn Terry" <donnte at microsoft dot com>, gcc at gcc dot gnu dot org
- Date: Tue, 04 Jun 2002 17:10:47 +0200
- Subject: Re: Mainline does not bootstrap for more than a week (Re: Newestgcc memory leak on gdb (heads up, only))
- References: <21721.1022777233@porcupine.cygnus.com><jeg003tnee.fsf@sykes.suse.de>
Andreas Schwab <schwab@suse.de> writes:
|> law@redhat.com writes:
|>
|> |> In message <jey9e1yasz.fsf@sykes.suse.de>, Andreas Schwab writes:
|> |> > "Donn Terry" <donnte@microsoft.com> 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.
|>
|> The memory leak is still present. Has anyone an idea how to fix that?
|> Bootstrap is broken for more than a week now!
Filed as PR bootstrap/6929.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."