From: Glyph Lefkowitz <glyph@divmod.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
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 17:14:53 -0400 [thread overview]
Message-ID: <1092690893.3394.27.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0408161247040.2666@dragon.hygekrogen.localhost>
On Mon, 2004-08-16 at 12:48 +0200, Jesper Juhl wrote:
> juhl@dragon:~$ gcc signal-bug.c -Wall -lutil -lpthread -o signal-bug; ./signal-bug
> Completed.
> juhl@dragon:~$ cat /proc/version
> Linux version 2.6.8.1 (juhl@dragon) (gcc version 3.4.1) #1 Sun Aug 15 22:01:56 CEST 2004
>
> glibc is 2.3.2
Thanks for the feedback. I will test with 2.6.8.1 myself, just to be
sure, but for those interested in the problem, I've included a few other
recordings of results I got on hosts with a variety of architectures and
kernel versions.
I could swear I tested this on a different host already, but I can't
find the results, so I will build a 2.6.8.1 without debian patches, just
to be sure.
glyph@trogdor:~% gcc signal-bug.c -Wall -lutil -lpthread -o signal-bug; ./signal-bug
Died.
glyph@trogdor:~% cat /proc/version
Linux version 2.6.7-1-686 (dilinger@toaster.hq.voxel.net) (gcc version 3.3.4 (Debian 1:3.3.4-2)) #1 Thu Jul 8 05:36:53 EDT 2004
glyph@trogdor:~% dpkg -l libc6 | tail -1
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries and Timezone
glyph@kazekage:~% gcc signal-bug.c -Wall -lutil -lpthread -o signal-bug; ./signal-bug
Died.
glyph@kazekage:~% cat /proc/version
Linux version 2.6.7-1-k7 (dilinger@toaster.hq.voxel.net) (gcc version 3.3.4 (Debian 1:3.3.4-2)) #1 Thu Jul 8 06:45:35 EDT 2004
glyph@kazekage:~% dpkg -l libc6 | tail -1
ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries and Timezone
glyph@wolfwood:~$ gcc signal-bug.c -Wall -lutil -lpthread -o signal-bug; ./signal-bug
Completed.
glyph@wolfwood:~$ cat /proc/version
Linux version 2.4.25vm-1um (root@shared4.tummy.com) (gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1)) #2 Fri Feb 20 14:03:26 MST 2004
glyph@wolfwood:~$ dpkg -l libc6 | tail -1
ii libc6 2.3.1-16 GNU C Library: Shared libraries and Timezone
glyph@pyramid:~% gcc signal-bug.c -Wall -lutil -lpthread -o signal-bug; ./signal-bug
Completed.
glyph@pyramid:~% cat /proc/version
Linux version 2.4.18 (root@pyramid.twistedmatrix.com) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 SMP Wed Feb 25 14:26:24 MST 2004
glyph@pyramid:~% dpkg -l libc6 | tail -1
ii libc6 2.2.5-11.5 GNU C Library: Shared libraries and Timezone
glyph@watt:~$ gcc signal-bug.c -Wall -lutil -lpthread -o signal-bug; ./signal-bug
Completed.
glyph@watt:~$ cat /proc/version
Linux version 2.4.25 (root@sparesolo20040319) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Wed Apr 7 16:22:47 MDT 2004
glyph@watt:~$ dpkg -l libc6 | tail -1
ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries and Timezone
glyph@erlang:~$ gcc signal-bug.c -Wall -lutil -lpthread -o signal-bug; ./signal-bug
Completed.
glyph@erlang:~$ cat /proc/version
Linux version 2.6.4 (root@erlang) (gcc version 3.3.3 (Debian 20040320)) #10 Mon Mar 22 20:01:54 EST 2004
glyph@erlang:~$ dpkg -l libc6 | tail -1
ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries and Timezone
prev parent reply other threads:[~2004-08-16 21:14 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
2004-08-16 10:48 ` Jesper Juhl
2004-08-16 21:14 ` Glyph Lefkowitz [this message]
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=1092690893.3394.27.camel@localhost \
--to=glyph@divmod.com \
--cc=juhl-lkml@dif.dk \
--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