Re: GCJ 3.3 LEAKS Throwable & Derived Classes

[Andi Vajda <andi at osafoundation dot org>]

On Sat, 19 Nov 2005, Andrew Haley wrote:

> Andi Vajda writes:
> >
> > The capability I'm most interested in is creating a shared library that is
> > statically linked with libgcj.a. So far, I've only been able to do this with
> > gcj 3.4.2 and gcj 3.4.4 on Windows.
>
> What do you mean, exactly?  Did you try in on some other OS and have
> it fail?

I mean creating a .so linked statically with libgcj.a. That way, I link in 
only what I use from libgcj and create a much smaller shared library. Yes, 
that prevents dynamic class loading but my app doesn't do that.
I tried it on Linux and Mac OS X with gcj 3.4.3 and the process crashes 
instantly upon loading the resulting .so (a python extension).
I haven't tried it yet with the latest gcc 4.1 snapshot, I should have more 
details once I do.

> I have heard that there are problems with gcj and DLLs on Windows, but
> I would expect this to work with gcj 4.x on other operating systems.

I haven't tried gcj 4.x on Windows. I have heard of the same problems and 
3.4.2 and 3.4.4 seem to work well enough. The reason I keep trying newer ones 
on Linux and OS X is that there I have not been able to link my shared 
library the same way and endup having to ship an extra 40 Mb of unused java 
runtime.

Andi..