Bug 163228 - libc.info about threads are too misleading
libc.info about threads are too misleading
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: glibc (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-07-14 05:19 EDT by Suzuki Takashi
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-25 16:04:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Suzuki Takashi 2005-07-14 05:19:33 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
Info document in glibc (libc.info) describes LinuxThreads.
But when running or compiling a program, NPTL is used instead by default.
There are perhaps some inappropriate explanations against NPTL.
That's too misleading for general users.

A few things I noticed were:
. Cancellation points are too limited and eg. select is not a cancellation point.
  (on NPTL, cancellation points are conformed to POSIX standard and
  almost all syscalls are cancellation points).
. pthread_cond_timedwait may return EINTR
  (one in LinuxThread also didn't return EINTR since glibc-2.1.3 though).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Invoke info libc.
2. Search Cancellation or pthread_cond_timedwait.

Additional info:
Comment 1 Jakub Jelinek 2005-07-14 05:27:38 EDT
For NPTL, the documentation is at
or in the 3p section of manual pages.
info libc thread section simply documents LinuxThreads, so you shouldn't
be using it when writing NPTL (or portable POSIX threads) programs.
Comment 2 Suzuki Takashi 2005-07-14 06:13:33 EDT
I understand what you are saying.
But is there any documentation a general user can see at a glance
that he or she should't consult info.libc about threads?
Comment 3 Ulrich Drepper 2005-07-25 16:04:02 EDT
Use the POSIX man pages we ship (as Jakub pointed out) or buy a book on POSIX
threads.  Nobody has volunteered to write decent documentation for the upstream
glibc so there is nothing for us to import.

If you have a RHEL license and insist of RH providing such documentation then
talk to your Red Hat representative.

Note You need to log in before you can comment on or make changes to this bug.