lkml.org 
[lkml]   [1997]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: why do we put code onto the stack when doing a signal?
On Tue, 15 Apr 1997, Mark Hemment wrote:

> Er, hmmmm, (moment of embarrasment), I wrote the original SCO stuff.

Aha! Bring on the comfy chair, lads!

> > The "standard" handler has (int, sigcontext) where sigcontext is
> > a Linux extension. The POSIX handler is (int, siginfo, sigcontext).
>
> Last time I checked, POSIX said nothing about this (but that was some
> time ago). SA_SIGINFO (and hence siginfo_t and u_context_t) are SVID-III.

SA_SIGINFO is also POSIX.4. I guess we know where it came from now :-).

> > The better solution (IMHO) is to always deliver siginfo. It only
> > breaks a few non-portable applications anyway and the alternative
> > is increased complexity and bloat.
>
> And it breaks iBCS2!

Oh bugger! Don't you just *love* standards? :-(

Mike

--
.----------------------------------------------------------------------.
| Mike Jagdis | Internet: mailto:mike@roan.co.uk |
| Roan Technology Ltd. | |
| 54A Peach Street, Wokingham | Telephone: +44 118 989 0403 |
| RG40 1XG, ENGLAND | Fax: +44 118 989 1195 |
`----------------------------------------------------------------------'


\
 
 \ /
  Last update: 2005-03-22 13:39    [W:0.037 / U:0.236 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site