This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/10320] New: erand48 implementation not thread safe but POSIX says it should be
- From: "simon at josefsson dot org" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 23 Jun 2009 19:25:37 -0000
- Subject: [Bug libc/10320] New: erand48 implementation not thread safe but POSIX says it should be
- Reply-to: sourceware-bugzilla at sourceware dot org
POSIX specification for erand48:
http://www.opengroup.org/onlinepubs/9699919799/functions/erand48.html
It doesn't say the function may be non-reentrant, which IIUC, means it should be
thread safe. However the implementation of erand48 does use a global variable:
http://sourceware.org/git/?p=glibc.git;a=blob;f=stdlib/erand48.c;hb=HEAD
The variable is __libc_drand48_data and is defined in:
http://sourceware.org/git/?p=glibc.git;a=blob;f=stdlib/drand48-iter.c;hb=HEAD
I can't find anyplace where it is made thread-local, so I'm assuming it is a
real global variable.
As far as I can tell, there is no requirement in the specification that erand48
update the global drand48 state.
--
Summary: erand48 implementation not thread safe but POSIX says it
should be
Product: glibc
Version: 2.11
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: simon at josefsson dot org
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10320
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.