This is the mail archive of the java-discuss@sources.redhat.com mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: GCJ Bug accessing field of inner class (gcc version 2.97 20010117)


> -----Original Message-----
> From: Barnet Wagman [mailto:wagman@enteract.com]
> There shouldn't be any large memory requests being generated; my test
> program
> just assigne one string and one int, in a constructor called 
> only once.
> 
> Is there a way to turn off the gcc when compiling with gcj?  
> I'd like to
> see if
> that makes any difference.
> 
You can turn of the garbage collector by either building without it (and
effectively using malloc), or by setting GC_dont_gc to prevent collections
from starting.  But I would guess that setting a gdb breakpoint in
GC_default_warn_proc, and looking at the call chain, might be more
informative.  I would guess that an allocation function is being passed a
bogus value as the object size.  But that's only a guess.

What platform are you running on?  Is the failure instantaneous, or do you
hear the disk for a while, as it garbage-collects repeatedly, before you get
the warning message?  If this is a standard platform, and the failure is
instantaneous, I would doubt that it's a collector problem.  This is not a
common collector failure mode.

Hans

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]