This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: Linking libgcj, and Java security
- From: Jeff Sturm <jsturm at one-point dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: "'Anthony Green'" <green at redhat dot com>, Andrew Haley <aph at redhat dot com>, <java at gcc dot gnu dot org>
- Date: Wed, 4 Dec 2002 22:31:20 -0500 (EST)
- Subject: RE: Linking libgcj, and Java security
On Wed, 4 Dec 2002, Boehm, Hans wrote:
> Do we all agree on what the CNI rules are about pointers to collectable
> objects in C/C++ data structures/libraries?
My hunch is it doesn't make much sense to worry about pointers in non-java
libraries that aren't linked to libgcj (e.g. libz.so).
> I have a secondary concern about the use of static constructors in all
> of this. Is there a way to avoid them?
I don't know.
> My recollection is that
> ordering issues eventually got in the way of most other attempts to use
> constructors in libgcj. The collector now avoids them. Their use here
> also seems brittle to me since the garbage collector (and presumably
> some Java code?) can be run before main().
I think Bryce eliminated most static initializers in the code, so they are
only used to register classes and resources. That seems pretty safe.
Jeff