Re: [Sablevm-developer] SA_SIGINFO undefined

[Julio M. M. V. <jm...@me...>]

On Sat, 27 Mar 2004 12:16:24 -0500
"Grzegorz B. Prokopski" <ga...@de...> wrote:

> 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.
>=20
> 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.
>=20
> 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.

That's indeed better.  The attached patch should do it: it checks for sigin=
fo
and, if it's not available, it disables all signals; but if it is, "signals
for exceptions" behavior is preserved.  Also avoids the ugly "#define sigin=
fo_t
void" hack of the previous patch.

This should help Cygwin too, as I read in another post ;)

Let's see if it's better now.  Cheers.

--=20
Julio M. Merino Vidal <jm...@me...>
The NetBSD Project - http://www.NetBSD.org/