Re: runtime error with own *.so

[Hans Boehm <Hans dot Boehm at hp dot com>]

I would place a breakpoint on the line in boehm-gc/alloc.c that
generates this message, and see what's going on.  If you're not
really out of memory, it's probably a bogus size argument to the
allocator.  Without a stack trace, I have no idea where that came
from.

Hans

On Sat, 29 Jan 2005, Jochen Rassler wrote:

> Hi guys.
>
> I have a runtime problem and don't know were to look for it.
>
> I've helped Ivan to port swtfox to gcj and have managed to build a
> native library.
> After that i built a simple testapp, a shell with a button in it, no
> functionality, just that.
> The test app is linked against the shared libswt-fox.so (which is
> actually linked against shared libswt-fox-3004.so).
>
> As soon as i start the test app i get the following output:
>
> 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?
>
> thanks in advance
> 	Jochen
>
>