NSIG wrong on Linux (amd64 and m68k, at least)
Thorsten Glaser
tg@mirbsd.de
Fri May 18 18:35:00 GMT 2012
Hi,
I just noticed NSIG was 65 on Debian/m68k with (e)glibc, and looked,
and it’s the same on amd64.
hpa said that it’s probably an off-by-one error, that someone
confused [32;64[ with [32;64] and that there are 32 RT signals
on Linux/x86_64 but changing SIGRTMAX would be messy.
The current source code still has this possible off-by-one:
http://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/bits/signum.h;h=3e485f6ed40ac289738e1a187a4732b45e61246b;hb=HEAD
→ line 68: #define _NSIG 65
bye,
//mirabilos, who’s doing too much libc work recently…
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
More information about the Libc-alpha
mailing list