From: "H. J. Lu" <hjl@lucon.org>
To: Jes Sorensen <jes@trained-monkey.org>
Cc: libc-hacker@sources.redhat.com
Subject: Re: 2.2.x mips signal crash
Date: Thu, 31 Oct 2002 18:44:00 -0000 [thread overview]
Message-ID: <20021031115701.A20971@lucon.org> (raw)
In-Reply-To: <200210311950.g9VJoST18983@trained-monkey.org>; from jes@trained-monkey.org on Thu, Oct 31, 2002 at 02:50:28PM -0500
On Thu, Oct 31, 2002 at 02:50:28PM -0500, Jes Sorensen wrote:
> Hi
>
> We are chasing a problem on Linux/mips with glibc-2.2.x, which I am not
> sure whether is a kernel bug or a libc bug. We haven't been able to
> reproduce it under Linux/x86 or Linux/ia64 so far though.
>
> Basically what seems to be happening is the following, a task is
> spawned from fork(), the child sends some signals to the parent after
> which it exits.
>
> The parent exits before the signals arrives and a signal is delivered
> some time after reaching exit(). As the signal handler is using
> printf() we get an explosion since the file descriptor seems to be
> gone (munmap()).
>
> My question is as follows: Is one required to wait for signal delivery
> in the parent before exiting or unregister the signal handlers? or is
> it a genuine bug?
>
> Any suggestions?
>
A testcase?
H.J.
next prev parent reply other threads:[~2002-10-31 19:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-31 11:57 Jes Sorensen
2002-10-31 18:44 ` H. J. Lu [this message]
[not found] ` <m37kfyvwin.fsf@trained-monkey.org>
2002-11-02 10:12 ` H. J. Lu
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=20021031115701.A20971@lucon.org \
--to=hjl@lucon.org \
--cc=jes@trained-monkey.org \
--cc=libc-hacker@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).