From: Nix <nix@esperi.org.uk>
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: Miquel van Smoorenburg <miquels@cistron.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Thread and process dentifiers (CPU affinity, kill)
Date: Mon, 23 May 2005 13:56:57 +0100 [thread overview]
Message-ID: <87ekbyf6cm.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20050520201255.GG23621@csclub.uwaterloo.ca> (Lennart Sorensen's message of "20 May 2005 21:14:29 +0100")
On 20 May 2005, Lennart Sorensen prattled cheerily:
> Maybe Debian compiled their glibc to not do NPTL on i386 yet. Not sure.
This is not the case. Proof from ps -FT output:
mysql 8473 8473 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
mysql 8473 8475 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
mysql 8473 8476 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
mysql 8473 8477 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
mysql 8473 8478 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
mysql 8473 8479 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
mysql 8473 8480 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
mysql 8473 8481 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
mysql 8473 8482 8472 0 29110 14056 0 May22 pts/1 /usr/sbin/mysqld
> Hmm, after checking, it turns out if you use errno in your program, it
> drops to linuxthreads, while using #include <errno.h> makes it able to
> use NPTL when using 2.6 kernel.
This is a distribution-specific patch. glibc as shipped by the FSF simply
refuses to run programs that reference the errno symbol: errno is no
longer an exported symbol at all. (This is reasonable, as such programs
would fail to work on a multithreaded NPTL program in any case.)
The only valid way to gain access to the errno symbol is to
#include <errno.h>. This has been true for as long as glibc2 has existed.
--
`Once again, I must remark on the far-reaching extent of my
ladylike nature.' --- Rosie Taylor
next prev parent reply other threads:[~2005-05-23 12:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 18:00 Thread and process dentifiers (CPU affinity, kill) Olivier Croquette
2005-05-19 18:23 ` Lennart Sorensen
2005-05-19 19:46 ` Chris Friesen
2005-05-20 12:55 ` Lennart Sorensen
2005-05-20 14:51 ` Olivier Croquette
2005-05-20 16:53 ` Lennart Sorensen
2005-05-20 18:13 ` Miquel van Smoorenburg
2005-05-20 20:12 ` Lennart Sorensen
2005-05-23 12:56 ` Nix [this message]
2005-05-20 20:17 ` Olivier Croquette
2005-05-20 20:38 ` Lee Revell
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=87ekbyf6cm.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=miquels@cistron.nl \
/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