The following issue has been UPDATED.
======================================================================
http://austingroupbugs.net/view.php?id=97
======================================================================
Reported By: msbrown
Assigned To: ajosey
======================================================================
Project: 1003.1(2008)/Issue 7
Issue ID: 97
Category: System Interfaces
Type: Clarification Requested
Severity: Comment
Priority: normal
Status: Interpretation Required
Name: Mark Brown
Organization: IBM
User Reference:
Section: dlerror
Page Number: 730
Line Number: 24539
Final Accepted Text: http://austingroupbugs.net/view.php?id=97#c138
======================================================================
Date Submitted: 2009-06-29 20:14 UTC
Last Modified: 2009-06-29 20:15 UTC
======================================================================
Summary: per-thread dlerror strings
Description:
_____________________________________________________________________________
COMMENT Enhancement Request
Number 27
peter:xxxxxxxxx Defect in XSH dlerror (rdvk#
1)
{none} Mon, 9 Mar 2009 16:01:28
GMT
_____________________________________________________________________________
The dlerror description can be read in such a way that per-thread
dlerror strings are not allowed, see the discussion thread
(http://www.opengroup.org/austin/mailarchives/ag/msg15415.html) on the
opengroup list for a variety of interpretations.
A number of implementations from multiple vendors have thread specific
errors, including: HP-UX, GNU/Linux with Glibc, Mac OS X, Tru64 Unix,
z/OS.
Information on most of these implementations was gathered with a small
test program, however z/OS information was provided by its manual
page:
http://publib.boulder.ibm.com/infocenter/zos/v1r10/index.jsp?topic=/com.ibm.zos.r10.bpxbd00/dlerror.htm
The standard should reflect existing practice and should explicitly
allow per-thread errors.
Desired Action:
Change:
The dlerror() function need not be thread-safe.
To:
The dlerror() function need not be thread-safe, however a
thread-safe implementation may return only errors that occur on the
current thread.
======================================================================
----------------------------------------------------------------------
(0000138) msbrown (manager) - 2009-06-29 20:15
http://austingroupbugs.net/view.php?id=97#c138
----------------------------------------------------------------------
-> Interps track
The standard is clear, however concerns are being fwd to the sponsor.
Change:
The dlerror() function need not be thread-safe.
To:
It is implementation-defined whether or not the dlerror() function is
thread-safe. A thread-safe implementation shall return only errors that
occur on the current thread.
The APPLICATION USAGE on p730 24555-24560 will need changing
Change from:
may reside in a static buffer
To:
resides in a buffer that is either system wide or thread wide
that may be overwritten on each call to dlerror()
|