extremely large expressions fail to compile

[Thomas Kunert]

Alexandre Oliva wrote:
> 
> David Whysong <dwhysong@physics.ucsb.edu> writes:
> 
> > [text/plain]
> > On 2 Oct 1998, Alexandre Oliva wrote:
> 
> >> David Whysong <dwhysong@physics.ucsb.edu> writes:
> >>
> >>> gcc: Internal compiler error: program cc1 got fatal signal 11
> >>
> >> A stack trace, as well as the source code in question, would certainly
> >> help.  bzip2/gzip base64/uuencode are fine.
> 
> > Here's the source.
> 
> I managed to compile it on a i686 running RedHat Linux 5.0+egcs 1.1.
> It had 400MB of free swap space when I started the compilation.
> 
> > I'm not sure how to do a stack trace, any pointers?
> 
> Run gcc with -v and find out the command line it uses to run cc1.
> Then, start cc1 with that command line within gdb, and wait until it
> crashes.  Then, type `where'; it will print a complete stack trace.

A shorter procedure is `gdb /rather/long/path/cc1 core', though.

--
Thomas Kunert