From: bert hubert <ahu@ds9a.nl>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: 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 22:18:26 +0100 [thread overview]
Message-ID: <20040131211826.GA24791@outpost.ds9a.nl> (raw)
In-Reply-To: <20040131204914.GB2160@kiste>
On Sat, Jan 31, 2004 at 09:49:14PM +0100, Matthias Urlichs wrote:
> 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 means your situation is different from what you describe. Python may
not in fact be doing 'real' threading on your setup. I suggest you try to
make the smallest possible python program that exhibits the program and send
it to the list.
Can you also run the Python program with LD_ASSUME_KERNEL=2.4 ? And my
program too.
Thanks.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-01-31 21:18 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 [this message]
2004-01-31 21:41 ` Matthias Urlichs
2004-01-31 21:52 ` Roland McGrath
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=20040131211826.GA24791@outpost.ds9a.nl \
--to=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
Powered by JetHome