From: "Joel Soete" <jsoe0708@tiscali.be>
To: "Matthew Wilcox" <willy@debian.org>
Cc: parisc-linux@lists.parisc-linux.org, debian-hppa@lists.debian.org
Subject: Re: [parisc-linux] glibc pthreads actual threads?
Date: Thu, 22 May 2003 11:52:54 +0200 [thread overview]
Message-ID: <3EC761C200001DBB@ocpmta7.freegates.net> (raw)
In-Reply-To: <20030519163245.GN16608@parcelfarce.linux.theplanet.co.uk>
>On Mon, May 19, 2003 at 06:27:41PM +0200, Joel Soete wrote:
>> But notice a very strange behaviour:
>> _the pid is not the same for each thread_ ??
>>
>> Having just a small sunos 5.8 with gcc-3.2.2 (but with native libpthread)
>> the pb does not occurs?
>>
>> Is it a limit of glibc (in general or in 2.3 only?) for all linux or only
>> hppa?
>
>it's a limit of your understanding ;-) POSIX specifies both behaviours
>are legitimate.
>
Just for remind and for those who also have this kind of philophical pb :-)).
In fact following test, an ardent discuss born here between high level system
engineer and one of them help me to find this interesting link:
<http://www.onlamp.com/pub/a/onlamp/2002/11/07/linux_threads.html>
Joel
---------------------------------
Vous surfez avec une ligne classique ?
Economisez jusqu'à 25% avec Tiscali Complete !
Offre spéciale : première année d'abonnement offerte.
... Plus d'info sur http://complete.tiscali.be
next prev parent reply other threads:[~2003-05-22 9:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 16:27 [parisc-linux] glibc pthreads actual threads? Joel Soete
2003-05-19 16:32 ` Matthew Wilcox
2003-05-19 16:32 ` Matthew Wilcox
2003-05-19 17:01 ` Joel Soete
2003-05-19 17:01 ` Joel Soete
2003-05-22 9:52 ` Joel Soete [this message]
2003-05-22 9:52 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2003-05-19 16:27 Joel Soete
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=3EC761C200001DBB@ocpmta7.freegates.net \
--to=jsoe0708@tiscali.be \
--cc=debian-hppa@lists.debian.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=willy@debian.org \
/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