All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Urlichs" <smurf@smurf.noris.de>
To: 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 22:41:25 +0100	[thread overview]
Message-ID: <20040131214125.GD2160@kiste> (raw)
In-Reply-To: <20040131211826.GA24791@outpost.ds9a.nl>

Hi,

bert hubert:
> This means your situation is different from what you describe. Python may
> not in fact be doing 'real' threading on your setup.

Well, the strace was from Python, so probably I was missing something...
but I can't think of anything not-real which Python does, except that it
does synchronize its internal state with MANY futex calls.  ;-)

> make the smallest possible python program that exhibits the program and send
> it to the list.
> 
I'll do that.

-- 
Matthias Urlichs     |     noris network AG     |     http://smurf.noris.de/

  reply	other threads:[~2004-01-31 22:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31 10:46 BUG: NTPL: waitpid() doesn't return? 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 [this message]
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=20040131214125.GD2160@kiste \
    --to=smurf@smurf.noris.de \
    --cc=ahu@ds9a.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=molnar@elte.hu \
    --cc=phil-list@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.