Bootstrap failure on Linux/x86-64

[Andreas Jaeger]

Kenneth Zadeck <zadeck@naturalbridge.com> writes:

> I am not going to see this failure on my machine.  I have a 2gb x86-64
> which will easily handle
> compiling this size file.   I was watching top as it compiled a stage2
> insn-addrtab, which I think is the largest function in the gcc stack
> and the VIRT topped at 501mb, which is no sweat for this machine.  You
> could argue, (and I would not disagree with you) that 501mb is not
> tolerable and is symptomatic of something bad happening.  There are,
> most likely storage leaks in the system.  But I do not think that you
> are going to necessarily find the problem by looking to see which
> version happens to crash on your machine.  The worst case senario is
> that this is just footprint creep and the version that failed was just
> the one the added the straw that broke the camels back with you
> particular config.

Ok, figured it out, it's my ulimit call:

ulimit -m 600000 -v 600000

So, memory usage has increased during the last days.  Don't we have
some automatic testers that look at memory usage as well?

Andreas
-- 
 Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/
  SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20060123/81923169/attachment.sig>