From: "drepper at redhat dot com" <sourceware-bugzilla@sources.redhat.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] [Bug nptl/651] The getpid() cache (and TLS) is not invalidated after clone() calls
Date: 12 Jan 2005 01:45:21 -0000 [thread overview]
Message-ID: <20050112014521.4294.qmail@sourceware.org> (raw)
In-Reply-To: <20050112011749.651.blaisorblade_spam@yahoo.it>
------- Additional Comments From drepper at redhat dot com 2005-01-12 01:45 -------
These confused ramblings are not helping at all. Is it so hard to write
I have this test program. When I run it like this I expect this output.
And reading "This is tested with any recent glibc" makes me want to smack
somebody. This problem has long been fixed so nobody with a recent glibc can
have experienced it.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
http://sources.redhat.com/bugzilla/show_bug.cgi?id=651
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-01-12 1:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050112011749.651.blaisorblade_spam@yahoo.it>
2005-01-12 1:21 ` [uml-devel] [Bug nptl/651] The getpid() cache (and TLS) is not invalidated after clone() calls blaisorblade_spam at yahoo dot it
2005-01-12 1:45 ` drepper at redhat dot com [this message]
2005-01-12 2:09 ` blaisorblade_spam at yahoo dot it
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=20050112014521.4294.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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.