Re: [PATCH] 2.3.18: siginfo data available for all signals

wtenhave@sybase.com
Wed, 15 Sep 1999 16:33:10 +0200 (CEST)

On 15 Sep, Jakub Jelinek wrote:
> As far as I understood rth wanted to do it that way, at least the comment in
> signal.c
> /* XXX: As an extension, support queueing exactly
> one non-rt signal if SA_SIGINFO is set, so that
> we can get more detailed information about the
> cause of the signal. */
> makes me think it.
> It makes a lot of sense to use siginfo_t for passing stuff like segfault
> address, segfault reason and the like and other Unices do it that way.
> What's so odd about that?
> Cheers, Jakub

Not having SA_SIGINFO is a real pain if you like to participate towards
certain application environments where you like to take appropriate
actions (fail-over, ....). Following this discussion I also have
constant trouble for these parts of code where I like to alter my
process context. Will setcontext(2) and getcontext(2) be part of 2.4?
Linux shows particular weak in this area ... or is my development
environment to far behind (kernel-2.2.12/glibc-2.1.1-6)?

-- Wim ten Have.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/