This is the mail archive of the
mailing list for the Cygwin project.
Re: SA_SIGINFO and signal info ?
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Samuel Thibault <samuel dot thibault at ens-lyon dot org>
- Cc: cygwin at cygwin dot com
- Date: Fri, 2 Dec 2005 18:56:56 -0500 (EST)
- Subject: Re: SA_SIGINFO and signal info ?
- References: <20051202230909.GM10913@bouh.residence.ens-lyon.fr>
- Reply-to: cygwin at cygwin dot com
On Sat, 3 Dec 2005, Samuel Thibault wrote:
> Cygwin defines SA_SIGINFO, but it doesn't seem to be implemented: the
> following program gets in "info" just 0x0 or a strange pointer. Could
> it be supported somehow? The bit of information I'd really need is
> info->si_code, so as to know whether the signal is sent by "kernelspace"
> (because of alarm, setitimer, ...) or by "userspace" (kill, raise).
AFAICS, this should work in the snapshots, according to
|\ _,,,---,,_ firstname.lastname@example.org
ZZZzz /,`.-'`' -. ;-;;,_ email@example.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html