This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: runtime error with own *.so
- From: Ranjit Mathew <rmathew at gmail dot com>
- To: java at gcc dot gnu dot org
- Date: Wed, 02 Feb 2005 10:39:29 +0530
- Subject: Re: runtime error with own *.so
- References: <1107039450.1597.90.camel@jogix.sojox> <41FFB587.8010803@redhat.com>
Bryce McKinlay wrote:
> Jochen Rassler wrote:
>
>
>>jochen> swtfox_gcj
>>GC Warning: Out of Memory! Returning NIL!
>>Exception in thread "main" java.lang.OutOfMemoryError
>> <<No stacktrace available>>
>>jochen>
>>
>>Which possible sources of errors are out there for this? Where might i
>>look for a solution? Any hints?
>>
>>
>
>
> This error is often caused by an inconsistent build and/or runtime
> environment: mixing .so/.o files compiled with different versions of
> GCJ, for example. When the BC-ABI is enabled by default, this issue
> should go away.
FWIW, on some rare occasions, I see the same
error with the Thread_Wait_2 testcase during
my regular bootstrap+testsuite cycles.
Unfortunately, when I try to run it manually
everything succeeds. The machine has 1GB of
physical RAM and 512MB of swap. It could therefore
be a "bogus" size argument to the GC as Hans
says, but I can't be completely sure. :-/
(The RAM on the box has been tested with
various memory testers including the vendor's
diagnostics utility as well as Memtest86 and
there are no problems.)
Ranjit.
--
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.hostingzero.com/