safety of GCJ-generated code

Wed Dec 19 02:56:00 GMT 2001

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.