From: Martin Zwickel <martin.zwickel@technotrend.de>
To: Glyph Lefkowitz <glyph@divmod.com>
Cc: 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:11:36 +0200 [thread overview]
Message-ID: <20040816121136.49bb3fc2@phoebee> (raw)
In-Reply-To: <1092650465.3394.13.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]
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
--
MyExcuse:
Flat tire on station wagon with tapes. ("Never underestimate the
bandwidth of a station wagon full of tapes hurling down the highway"
Andrew S. Tannenbaum)
Martin Zwickel <martin.zwickel@technotrend.de>
Research & Development
TechnoTrend AG <http://www.technotrend.de>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-16 10:11 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 [this message]
2004-08-16 10:18 ` Paweł Sikora
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=20040816121136.49bb3fc2@phoebee \
--to=martin.zwickel@technotrend.de \
--cc=glyph@divmod.com \
--cc=linux-kernel@vger.kernel.org \
/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