Messages in this thread | | | Date | Sun, 14 Nov 1999 02:12:57 +0100 (MET) | From | Andries.Brouwer@cwi ... | Subject | Re: [PATCH] signals causing coredumps |
| |
On Sun, Nov 14, 1999 at 01:46:16AM +0100, Ralf Baechle wrote: > On Sat, Nov 13, 1999 at 05:41:40PM +0100, Andries.Brouwer@cwi.nl wrote: > > > so, even though the signals need not do anything special, > > they should at least exist. However, SIGSYS is defined only > > on mips/alpha/sparc* but not on i386 etc. > > On MIPS I only define it because it's an ABI item. > > Ralf
Of course - only the sparc code actually uses it.
Some people will say that providing this item is a job for libc, and I might agree some other day, but in this case the standard continues and tells us to produce a coredump for it (that is, treat it like SIGQUIT and the rest), so that the kernel code also must test for equality with SIGSYS.
(And besides, apart from coredumps, giving the definition in libc (i) is not done today, (ii) would be a very messy affair since the signal numbers differ for the 9 architectures. My patch is really the easiest way to get compliance on this point.)
Andries
- 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/
| |