Messages in this thread | | | Date | 03 Jul 2004 15:54:00 +0200 | From | (Kai Henningsen) | Subject | Re: [patch] signal handler defaulting fix ... |
| |
froese@gmx.de (Edgar Toernig) wrote on 29.06.04 in <2cfBL-6uJ-9@gated-at.bofh.it>:
> Not the signal part. It was written for libc5. There, signals set > with signal(2) were reset when raised (SysV-style). Leaving such a > signal handler with longjmp was perfectly valid. > > Glibc2 changed the rules: signals set with signal(2) are not reset > but blocked during delivery (BSD-style). It worked for a while > because the kernel ignored the sigmask for some signals. > > So, if one is to blame then glibc2 by breaking compatibility.
You might want to study /usr/include/signal.h and /usr/include/feature.h.
And then you might try stuff like -D_SVID_SOURCE or -Dsignal=sysv_signal, for example.
And stop blaming glibc for your failures.
MfG Kai - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |