java/6462: jc1 "Cannot allocate xxx bytes after allocating yyyy bytes" message

java/6462: jc1 "Cannot allocate xxx bytes after allocating yyyy bytes" message

[me]

>Number:         6462
>Category:       java
>Synopsis:       jc1 "Cannot allocate xxx bytes after allocating yyyy bytes" message
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Apr 25 13:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     me@christltimon.de
>Release:        gcc-3.0.4
>Organization:
>Environment:
Redhat 7.2

gcc 3.0.4 built from source with "make bootstrap-lean", using gcc 2.96. I omitted the testing step.

AMD Athlon 900 MHz with 512MB RAM and plenty of diskspace
>Description:
jc1 exits with the following error message when I try to compile a java file. It also happens when I try to compile already compiled .class files.


gcc --verbose  -c -o Board.o Board.java
Reading specs from /home/tmp/christl/gcc-3.0.4/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.4/specs
Configured with: ../gcc-3.0.4/configure --prefix=/home/cip/christl/tmp/gcc-3.0.4
Thread model: single
gcc version 3.0.4
 /home/tmp/christl/gcc-3.0.4/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.0.4/jc1 Board.java -quiet -dumpbase Board.java -version -o /tmp/ccwevWAf.s
GNU Java version 3.0.4 (i686-pc-linux-gnu)
        compiled by GNU C version 3.0.4.

jc1: Cannot allocate 1768386413 bytes after allocating 179016 bytes

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

Re: java/6462: jc1 "Cannot allocate xxx bytes after allocating yyyy bytes" message

[Tom Tromey]

The following reply was made to PR java/6462; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: Christl Timon <me@christltimon.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/6462: jc1 "Cannot allocate xxx bytes after allocating yyyy bytes" message
Date: 29 Apr 2002 15:36:06 -0600

 >>>>> ">" == Christl Timon <me@christltimon.de> writes:
 
 I've CC'd gcc-gnats so that this will be logged in the PR.
 
 >> Note especially #2: The source line is
 
 >> zipf-> central_directory=ALLOC(zipf->dir_size+1);
 
 >> For a certain jar file in my $CLASSPATH (retroguard.jar, a bytecode
 >> optimizer and obfuscator) the value of zipf->dir_size is unusally large.
 >> Seems that the makers of retroguard have corrupted the jarfile with
 >> their own product. When I remove this jar file from my $CLASSPATH it works.
 
 Thanks for analyzing this.
 
 We definitely can't support cases where a jar file is intentionally
 corrupted like this.  jar files must conform to the spec.
 
 Perhaps we could change this xmalloc() to an ordinary malloc() and
 print a nicer error message before dying.  That's pretty low priority
 for me, but if you want to write a patch that would be helpful.
 
 Tom

Re: java/6462: jc1 "Cannot allocate xxx bytes after allocating yyyy bytes" message

[Tom Tromey]

The following reply was made to PR java/6462; it has been noted by GNATS.

From: Tom Tromey <tromey@redhat.com>
To: me@christltimon.de
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/6462: jc1 "Cannot allocate xxx bytes after allocating yyyy bytes" message
Date: 25 Apr 2002 23:34:38 -0600

 >>>>> ">" == me  <me@christltimon.de> writes:
 
 >> Number:         6462
 >> Synopsis:       jc1 "Cannot allocate xxx bytes after allocating yyyy bytes" message
 
 You haven't really given us enough information to help with this
 problem.  For instance, can you reproduce it with a small test case?
 
 gcc 3.1 is going to be released pretty soon.  Could you try compiling
 your program with the 3.1 snapshot?  That would be helpful.
 
 Tom