Re: [Sablevm-developer] SA_SIGINFO undefined

[Grzegorz B. P. <ga...@de...>]

W li=B6cie z pi=B1, 26-03-2004, godz. 18:18, Julio M. Merino Vidal pisze:=
=20
> - Move some #ifdef's around in error.c, to protect more code that uses =
siginfo
>   stuff.

The only problem is, that sometimes you want to disable signals for
performance resons and still be able to send SIGQUIT to get stack dump.
The --disable-signals-for-exceptions has it in its name. It is not
a general switch that enables/disables signals.

I think that based on the autodetection you wrote you could define
a symbol in configure, then use it to either disable SIGQUIT handling
completly, or to enable some special version of this handler.

Cheers,

					Grzegorz B. Prokopski
--=20
Grzegorz B. Prokopski <ga...@de...>
Debian GNU/Linux      http://www.debian.org
SableVM - LGPLed JVM  http://www.sablevm.org
Why SableVM ?!?       http://devel.sablevm.org/wiki/WhySableVM