Date: Sat, 7 Sep 2002 13:11:21 -0400 (EDT) From: Garrett Wollman <wollman@lcs.mit.edu> To: jmallett@FreeBSD.ORG Cc: arch@FreeBSD.ORG Subject: Re: CFR: signalinfo(3) Message-ID: <200209071711.g87HBLxO048550@khavrinen.lcs.mit.edu> In-Reply-To: <20020907022003.A66983@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20020907022003.A66983@FreeBSD.org> you write: >See, signal(3) installs handlers for the sa_handler variety of signal >handlers, and yet this is not the only type of handler one might want >to have, one might also want the "traditional" sa_sigaction handler >style, which includes siginfo_t, and struct sigcontext, both of which >are very useful, depending on the signal. Actually, those are new-style (POSIX Real-Time Signals) handlers. The traditional (Standard C) style takes a single argument. The really-old-fashioned (4.2BSD, pre-C89) handlers provided three arguments but they weren't the same as the three arguments used in RTS handlers and in any case we don't support that now. >So I wrote signalinfo(3) >which installs *those* kinds of signal handlers, no fuss. I'm confused. Why would you want to use this? There is already a perfectly good interface for installing Real-Time Signal handlers, and it's specified in the standard: sigaction(3). I don't think that this convenience function belongs in the C library. -GAWollman -- Garrett A. Wollman | [G]enes make enzymes, and enzymes control the rates of wollman@lcs.mit.edu | chemical processes. Genes do not make ``novelty- Opinions not those of| seeking'' or any other complex and overt behavior. MIT, LCS, CRS, or NSA| - Stephen Jay Gould (1941-2002) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209071711.g87HBLxO048550>