From: Roland McGrath <roland@redhat.com>
To: "Matthias Urlichs" <smurf@smurf.noris.de>
Cc: bert hubert <ahu@ds9a.nl>,
linux-kernel@vger.kernel.org, molnar@elte.hu,
phil-list@redhat.com
Subject: Re: BUG: NTPL: waitpid() doesn't return?
Date: Sat, 31 Jan 2004 13:52:43 -0800 [thread overview]
Message-ID: <200401312152.i0VLqh6W024564@magilla.sf.frob.com> (raw)
In-Reply-To: Matthias Urlichs's message of Saturday, 31 January 2004 21:49:14 +0100 <20040131204914.GB2160@kiste>
> Your test program works... except that it reports, when I strace it,
>
> [pid 10629] waitpid(10631, Process 10629 suspended
> <unfinished ...>
> [pid 10628] <... mmap2 resumed> ) = 0x41966000
> [pid 10630] waitpid(10632, Process 10630 suspended
> <unfinished ...>
>
> Those "Process ### suspended" messages did NOT happen with the Python
> script that exhibits the bug.
This is an strace bug. Because of goofy ptrace interactions, strace does
funny business with threads doing wait calls. strace should resume those
threads when the pids they are waiting for exit.
Make sure you are using the most current strace and if it's still not
different then report the strace bug (<strace-devel@lists.sourceforge.net>
or https://bugzilla.redhat.com are fine).
To research the issue thoroughly, you may have to avoid relying on strace
to tell you what calls your programs make.
next prev parent reply other threads:[~2004-01-31 21:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-31 10:46 Matthias Urlichs
2004-01-31 15:37 ` bert hubert
2004-01-31 15:51 ` Matthias Urlichs
2004-01-31 16:18 ` bert hubert
2004-01-31 18:15 ` Matthias Urlichs
2004-01-31 19:19 ` bert hubert
2004-01-31 20:49 ` Matthias Urlichs
2004-01-31 21:18 ` bert hubert
2004-01-31 21:41 ` Matthias Urlichs
2004-01-31 21:52 ` Roland McGrath [this message]
2004-01-31 19:02 ` Linus Torvalds
2004-01-31 20:00 ` Matthias Urlichs
2004-01-31 20:58 ` Linus Torvalds
2004-01-31 21:11 ` Matthias Urlichs
2004-01-31 22:52 ` Linus Torvalds
2004-01-31 22:29 ` Matthias Urlichs
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=200401312152.i0VLqh6W024564@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=molnar@elte.hu \
--cc=phil-list@redhat.com \
--cc=smurf@smurf.noris.de \
/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®