Re: reproducible bug in 2.2.19 & 2.4.x

Balazs Scheidler (
Sat, 29 Sep 2001 00:12:45 +0200

On Fri, Sep 28, 2001 at 03:15:32PM -0400, Mark Hahn wrote:
> seems like an interaction between your signal code and pthread,
> no obvious reason to blame the kernel:

If you check out the code again, you can see that I _don't_ have signal code
for SIGPIPE, it's SIG_IGN-ed. I only have signal handler for SIGSEGV, which
is executed when the bogus jump occurrs to 0x1.

I agree that this can be either a kernel, pthread or libc problem.

BTW: the SIGSEGV occurs on UP machine with SMP kernel as well.

PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at