From: "Paweł Sikora" <pluto@pld-linux.org>
To: Martin Zwickel <martin.zwickel@technotrend.de>
Cc: Glyph Lefkowitz <glyph@divmod.com>, linux-kernel@vger.kernel.org
Subject: Re: inconsistency in thread/signal interaction in 2.6.5 and previous vs. 2.6.6 and later (possibly a bug?)
Date: Mon, 16 Aug 2004 12:18:22 +0200 [thread overview]
Message-ID: <200408161218.23718.pluto@pld-linux.org> (raw)
In-Reply-To: <20040816121136.49bb3fc2@phoebee>
On Monday 16 of August 2004 12:11, Martin Zwickel wrote:
> On Mon, 16 Aug 2004 06:01:05 -0400
>
> Glyph Lefkowitz <glyph@divmod.com> bubbled:
> > Hello Kernel People,
> >
> > Firstly, here is a brief example of some code that behaves very
> > differently on 2.6.5 and 2.6.6:
> >
> > http://www.twistedmatrix.com/users/glyph/signal-bug.c
> >
> > I have verified that it says "Completed" on kernel 2.6.5, 2.6.3 and
> > 2.6.1, and says "Died" on 2.6.6, 2.6.7 and 2.6.8.1, so I am pretty
> > sure the difference is between 2.5.6 and 2.6.6.
>
> FYI:
> # gcc signal-bug.c -Wall -lutil -lpthread -o signal-bug; ./signal-bug
> Completed.
>
> # cat /proc/version
> Linux version 2.6.8-rc2-mm1 (root@phoebee) (gcc version 3.3.3 20040412
> (Gentoo Linux 3.3.3-r6, ssp-3.3.2-2, pie-8.7.6)) #1 Wed Jul 28 11:39:48
> CEST 2004
# gcc signal-bug.c -Wall -lpthread -lutil -o signal-bug; ./signal-bug
Died.
# cat /proc/version
Linux version 2.6.8 (pluto@vmx) (gcc version 3.4.2 20040806 (prerelease)
(PLD Linux)) #1 Sun Aug 15 19:58:30 CEST 2004
# rpm -q glibc
glibc-2.3.4-0.20040722.2+nptl
--
/* Copyright (C) 2003, SCO, Inc. This is valuable Intellectual Property. */
#define say(x) lie(x)
next prev parent reply other threads:[~2004-08-16 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 10:01 inconsistency in thread/signal interaction in 2.6.5 and previous vs. 2.6.6 and later (possibly a bug?) Glyph Lefkowitz
2004-08-16 10:11 ` Martin Zwickel
2004-08-16 10:18 ` Paweł Sikora [this message]
2004-08-16 10:48 ` Jesper Juhl
2004-08-16 21:14 ` Glyph Lefkowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200408161218.23718.pluto@pld-linux.org \
--to=pluto@pld-linux.org \
--cc=glyph@divmod.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.zwickel@technotrend.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox