Date: Sat, 2 Oct 1999 18:56:17 -0500 From: Alan Cox <alc@cs.rice.edu> To: Bruce Evans <bde@zeta.org.au> Cc: John Polstra <jdp@polstra.com>, "David O'Brien" <obrien@freebsd.org>, current@freebsd.org Subject: Re: Now that sigcontext is gone ... Message-ID: <19991002185617.L19202@cs.rice.edu> In-Reply-To: <Pine.BSF.4.10.9910030928230.4614-100000@alphplex.bde.org>; from Bruce Evans on Sun, Oct 03, 1999 at 09:42:45AM %2B1000 References: <XFMail.991002122051.jdp@polstra.com> <Pine.BSF.4.10.9910030928230.4614-100000@alphplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 03, 1999 at 09:42:45AM +1000, Bruce Evans wrote:
>
> I think the POSIX way is to use an auxiliary error code in siginfo_t to
> distinguish the causes of the signal. This only works for SA_SIGINFO
> handlers. We do something similar using the signal code of 3-arg signal
> handlers.
>
From Solaris 2.6 _AND_ Digital Unix 4.0E:
_________________________________________________________
Signal Code Definition
_________________________________________________________
SIGSEGV SEGV_MAPERR address not mapped to object
SEGV_ACCERR invalid permissions for mapped object
SIGBUS BUS_ADRALN invalid address alignment
BUS_ADRERR non-existent physical address
BUS_OBJERR object specific hardware error
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991002185617.L19202>