This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: safety of GCJ-generated code
- From: Andrew Haley <aph at cambridge dot redhat dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: Adam Megacz <gcj at lists dot megacz dot com>, java at gcc dot gnu dot org
- Date: Wed, 19 Dec 2001 10:55:28 +0000 (GMT)
- Subject: RE: safety of GCJ-generated code
- References: <40700B4C02ABD5119F000090278766443BEE4A@hplex1.hpl.hp.com>
Boehm, Hans writes:
> Note that the garbage collector is not aware of sigaltstack. It either
> needs to be adapted, or we need to make sure that it never catches a thread
> on the alternate stack. It may suffice to simply mask all signals in the
> SIGSEGV handler.
>
> Another problem with all of this is that on some platforms throwing an
> exception may require a large amount of allocation, e.g. to read in debug
> information for the stack unwinder. But on X86 that's hopefully not an
> issue.
It all gets very complicated, doesn't it? However, it looks like
sigaltstack is the only way we're going to get this to work.
Andrew.