This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: Linking libgcj, and Java security
- From: "Boehm, Hans" <hans_boehm at hp dot com>
- To: "'Anthony Green'" <green at redhat dot com>, Andrew Haley <aph at redhat dot com>
- Cc: Jeff Sturm <jsturm at one-point dot com>, "Boehm, Hans" <hans_boehm at hp dot com>, java at gcc dot gnu dot org
- Date: Wed, 4 Dec 2002 13:28:43 -0800
- Subject: RE: Linking libgcj, and Java security
Do we all agree on what the CNI rules are about pointers to collectable objects in C/C++ data structures/libraries?
I have a secondary concern about the use of static constructors in all of this. Is there a way to avoid them? 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().
Hans
> -----Original Message-----
> From: Anthony Green [mailto:green@redhat.com]
> Sent: Wednesday, December 04, 2002 1:01 PM
> To: Andrew Haley
> Cc: Jeff Sturm; Boehm, Hans; java@gcc.gnu.org
> Subject: RE: Linking libgcj, and Java security
>
>
> On Wed, 2002-12-04 at 12:10, Andrew Haley wrote:
> > Sounds good, if that's indeed the cause of the problem.
>
> Hmm.. but then this wouldn't catch pointers to collectable
> objects found
> in C/C++ data/bss.
>
> AG
>
>