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: Fri, 28 Sep 2001 20:30:19 +0200 [thread overview]
Message-ID: <20010928203019.A24999@balabit.hu> (raw)
In-Reply-To: <20010928130138.A19532@balabit.hu> <Pine.LNX.4.10.10109281121590.6506-100000@coffee.psychology.mcmaster.ca>
In-Reply-To: <Pine.LNX.4.10.10109281121590.6506-100000@coffee.psychology.mcmaster.ca>; from hahn@physics.mcmaster.ca on Fri, Sep 28, 2001 at 11:22:45AM -0400
On Fri, Sep 28, 2001 at 11:22:45AM -0400, Mark Hahn wrote:
> > - each thread logs messages using syslog (libc changes SIGPIPE settings
>
> it does syslog from within the signal handler? I doubt that's legal.
you are right, but the problem is that the handler gets called at all.
the sigsegv doesn't happen within the signal handler, if you look at the
backtrace, it happens during the write() syscall.
--
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
next prev parent reply other threads:[~2001-09-28 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 11:01 Balazs Scheidler
[not found] ` <Pine.LNX.4.10.10109281121590.6506-100000@coffee.psychology.mcmaster.ca>
2001-09-28 18:30 ` Balazs Scheidler [this message]
[not found] ` <Pine.LNX.4.10.10109281515050.6506-100000@coffee.psychology.mcmaster.ca>
2001-09-28 22:12 ` Balazs Scheidler
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
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=20010928203019.A24999@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
all inboxes | Powered by JetHome®