This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: shared library issues

From: Tom Tromey <tromey at redhat dot com>
To: Stéphane Konstantaropoulos <stephane at cs dot york dot ac dot uk>
Cc: Bryce McKinlay <mckinlay at redhat dot com>, Thomas Fitzsimmons <fitzsim at redhat dot com>, java at gcc dot gnu dot org
Date: 02 May 2005 17:35:27 -0600
Subject: Re: shared library issues
References: <1114909789.6751.54.camel@localhost.localdomain><1114910973.21901.41.camel@tortoise.toronto.redhat.com><42765809.1030104@redhat.com><1115074566.5052.12.camel@localhost.localdomain>
Reply-to: tromey at redhat dot com

>>>>> "Stéphane" == Stéphane Konstantaropoulos <stephane@cs.york.ac.uk> writes:

Stéphane> Would there be no way to do some - more dirty - thing like: dlopen
Stéphane> libgcj and dlclose it when no longer needed?

This sounds difficult.  You'd probably need hooks into the GC, and
you'd probably also want to figure out how to dlclose whatever
libraries might have been loaded by libgcj itself.  At that point you
might as well write DestroyJavaVM.

Tom

References:
- shared library issues
  - From: Stéphane Konstantaropoulos
- Re: shared library issues
  - From: Thomas Fitzsimmons
- Re: shared library issues
  - From: Bryce McKinlay
- Re: shared library issues
  - From: Stéphane Konstantaropoulos

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]