This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Get libffi closures to cope with SELinux execmem/execmod
- From: Andrew Haley <aph at redhat dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>, gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org
- Date: Thu, 18 Jan 2007 12:46:56 +0000
- Subject: Re: Get libffi closures to cope with SELinux execmem/execmod
- References: <ork5zkiz8v.fsf@redhat.com> <17839.26733.654885.743254@zebedee.pink>
Andrew Haley writes:
>
> When a Java object, such as a Class, is being finalized, it is
> reachable. So, disposing of the closures at this point is potentially
> dangerous. Please disable the call to
> _Jv_ClosureList::releaseClosures for the time being, and we'll
> investigate ways to defer the release until the class in unreachable.
> I know this will cause a small memory leak, but we'll live with that
> for the time being. (One idea I have is to mark the closures as dead,
> and then have a separate loop that reclaims them after all finalizers
> have run.)
Or, alterntatively, we'll be able to prove that my worries here are
unfounded, and we'll put the call back in.
Andrew.