This is the mail archive of the
java-discuss@sources.redhat.com
mailing list for the Java project.
RE: GCJ Bug accessing field of inner class (gcc version 2.97 20010117)
- To: "'Barnet Wagman'" <wagman at enteract dot com>, java-discuss at sources dot redhat dot com
- Subject: RE: GCJ Bug accessing field of inner class (gcc version 2.97 20010117)
- From: "Boehm, Hans" <hans_boehm at hp dot com>
- Date: Fri, 19 Jan 2001 11:23:25 -0800
> -----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