From: Blaisorblade <blaisorblade_spam@yahoo.it>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Bodo Stroesser" <bstroesser@fujitsu-siemens.com>,
stian@nixia.no,
"User-mode Linux Kernel Development"
<user-mode-linux-devel@lists.sourceforge.net>,
"Jeff Dike" <jdike@addtoit.com>,
"Roland Kaeser" <roli8200@yahoo.de>,
"Nuno Silva" <nuno.silva@vgertech.com>,
"Antoine Martin" <antoine@nagafix.co.uk>,
"Sven K�hler" <skoehler@upb.de>,
"Dennis Muhlestein" <devel@muhlesteins.com>
Subject: Re: [uml-devel] Re: Stop at startup on 2.6 NPTL hosts
Date: Wed, 10 Nov 2004 15:32:10 +0100 [thread overview]
Message-ID: <200411101532.11446.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <Pine.GSO.4.61.0411101342120.17015@waterleaf.sonytel.be>
On Wednesday 10 November 2004 13:47, Geert Uytterhoeven wrote:
> On Wed, 10 Nov 2004, Bodo Stroesser wrote:
> > Geert Uytterhoeven wrote:
> > > On Wed, 10 Nov 2004 stian@nixia.no wrote:
> Yes, according to the man page getpid returns the process ID of the current
> process. Doesn't it do that?
> [ digging into mail archives ]
> Sorry, I misunderstood. Yes, this must be a glibc bug.
> Sorry for the confusion...
> Gr{oetje,eeting}s,
> Geert
What's more, I think that fork() cannot be a plain syscall or it would
experience the same bug.
So, the same thing applies to clone().
Btw, the issue is not only with getpid(), I guess, but rather with any
__thread variable (the so-called Thread Local Storage).
Bye
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
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:[~2004-11-10 14:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 9:26 [uml-devel] UML Kernel 2.6.7 Nothing happens Roland Kaeser
2004-11-02 18:52 ` Stop at startup on 2.6 NPTL hosts (was: Re: [uml-devel] UML Kernel 2.6.7 Nothing happens) Blaisorblade
2004-11-02 23:43 ` [uml-devel] Re: Stop at startup on 2.6 NPTL hosts Sven Köhler
2004-11-03 3:04 ` Nuno Silva
2004-11-03 8:32 ` Gerd Knorr
2004-11-03 15:59 ` Blaisorblade
2004-11-03 20:10 ` Gerd Knorr
2004-11-03 22:17 ` Blaisorblade
2004-11-03 22:17 ` Blaisorblade
2004-11-04 8:40 ` Nuno Silva
2004-11-09 16:42 ` Bodo Stroesser
2004-11-09 17:29 ` Adam Heath
2004-11-09 17:32 ` Bodo Stroesser
2004-11-09 18:23 ` Bodo Stroesser
2004-11-09 19:11 ` Blaisorblade
2004-11-10 8:36 ` stian
2004-11-10 9:07 ` Geert Uytterhoeven
2004-11-10 12:15 ` Bodo Stroesser
2004-11-10 12:47 ` Geert Uytterhoeven
2004-11-10 14:32 ` Blaisorblade [this message]
2004-11-10 14:44 ` Sven Köhler
2004-11-10 21:19 ` Henrik Nordstrom
2004-11-15 17:17 ` Blaisorblade
2004-11-10 17:16 ` Blaisorblade
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=200411101532.11446.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=antoine@nagafix.co.uk \
--cc=bstroesser@fujitsu-siemens.com \
--cc=devel@muhlesteins.com \
--cc=geert@linux-m68k.org \
--cc=jdike@addtoit.com \
--cc=nuno.silva@vgertech.com \
--cc=roli8200@yahoo.de \
--cc=skoehler@upb.de \
--cc=stian@nixia.no \
--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.