From: Balazs Scheidler <bazsi@balabit.hu>
To: Mark Hahn <hahn@physics.mcmaster.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reproducible bug in 2.2.19 & 2.4.x
Date: Sat, 29 Sep 2001 00:12:45 +0200 [thread overview]
Message-ID: <20010929001245.A25486@balabit.hu> (raw)
In-Reply-To: <20010928203019.A24999@balabit.hu> <Pine.LNX.4.10.10109281515050.6506-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10109281515050.6506-100000@coffee.psychology.mcmaster.ca>; from hahn@physics.mcmaster.ca on Fri, Sep 28, 2001 at 03:15:32PM -0400
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:
[snip]
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.
--
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
next prev parent reply other threads:[~2001-09-28 22:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 11:01 reproducible bug in 2.2.19 & 2.4.x Balazs Scheidler
[not found] ` <Pine.LNX.4.10.10109281121590.6506-100000@coffee.psychology.mcmaster.ca>
2001-09-28 18:30 ` Balazs Scheidler
[not found] ` <Pine.LNX.4.10.10109281515050.6506-100000@coffee.psychology.mcmaster.ca>
2001-09-28 22:12 ` Balazs Scheidler [this message]
2001-10-01 10:03 ` Balazs Scheidler
2001-10-02 8:31 ` Balazs Scheidler
[not found] ` <20011003125319.A32248@sci41.imag.fr>
2001-10-03 11:41 ` reproducible bug in 2.2.19 & 2.4.x [lkml] Balazs Scheidler
-- strict thread matches above, loose matches on Subject: below --
2001-09-28 11:38 reproducible bug in 2.2.19 & 2.4.x Rainer Keller
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=20010929001245.A25486@balabit.hu \
--to=bazsi@balabit.hu \
--cc=hahn@physics.mcmaster.ca \
--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