From: Arun Sharma <arun.sharma@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: wait4 causes segfault in i386 chroot
Date: Thu, 10 Jun 2004 19:08:26 +0000 [thread overview]
Message-ID: <40C8B1AA.5040307@intel.com> (raw)
In-Reply-To: <20040610051605.GA21936@cse.unsw.EDU.AU>
On 6/9/2004 10:16 PM, Ian Wienand wrote:
> I've tracked it down to doing a wait/waitpid/wait4 (they all end up in
> wait4) in a sigchld signal handler. If I do a minimal test case where
> I catch the sigchld and wait, once the call returns it segfaults as in
> this trace (gdb can't seem to give a good backtrace).
>
I recall seeing this problem earlier. But I'm unable to reproduce it now. I tried with 2.4.x and 2.6.6. Will try 2.6.7-rc3 later today. What was your glibc version ?
-Arun
next prev parent reply other threads:[~2004-06-10 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 5:16 wait4 causes segfault in i386 chroot Ian Wienand
2004-06-10 19:08 ` Arun Sharma [this message]
2004-06-11 2:02 ` Ian Wienand
2004-06-11 20:13 ` Arun Sharma
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=40C8B1AA.5040307@intel.com \
--to=arun.sharma@intel.com \
--cc=linux-ia64@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