View Issue Details

IDProjectCategoryView StatusLast Update
00000971003.1(2008)/Issue 7System Interfacespublic2013-04-16 13:06
Reporterpogma Assigned Toajosey  
PrioritynormalSeverityCommentTypeClarification Requested
Status ClosedResolutionAccepted As Marked 
NamePeter O'Gorman
Organization
User Reference
Sectiondlerror
Page Number730
Line Number24539
Interp StatusApproved
Final Accepted Text0000097:0000138
Summary0000097: 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 ActionChange:
     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.
Tagstc1-2008

Relationships

related to 0000075 Closedajosey functions that are allowed to overwrite returned static data 

Activities

msbrown

2009-06-29 20:15

manager   bugnote:0000138

Last edited: 2009-10-12 05:50

Interpretation response
------------------------
The standard states the requirements for dlerror() strings
and conforming implementations must conform to this. However, concerns
have been raised about this which are being referred to the sponsor."

Rationale:
-------------
None.

Notes to the Editor (not part of this interpretation):
-------------------------------------------------------


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()

nick

2009-08-06 16:30

manager   bugnote:0000190

See also bug 0000075, which modifies some of the same words.

ajosey

2011-03-30 09:52

manager   bugnote:0000729

When applying the change for dlerror() in the draft TC1-2008, bug 75 was also taken into account . This meant that the proposed APPLICATION USAGE text
was unnecessary as bug 75 added text covering this behavior.

Issue History

Date Modified Username Field Change
2009-06-29 20:14 msbrown New Issue
2009-06-29 20:14 msbrown Status New => Under Review
2009-06-29 20:14 msbrown Assigned To => ajosey
2009-06-29 20:14 msbrown Name => Mark Brown
2009-06-29 20:14 msbrown Organization => IBM
2009-06-29 20:14 msbrown Section => dlerror
2009-06-29 20:14 msbrown Page Number => 730
2009-06-29 20:14 msbrown Line Number => 24539
2009-06-29 20:15 msbrown Note Added: 0000138
2009-06-29 20:15 msbrown Status Under Review => Interpretation Required
2009-06-29 20:15 msbrown Resolution Open => Accepted As Marked
2009-06-29 20:15 msbrown Final Accepted Text => 0000097:0000138
2009-07-01 18:07 Don Cragun Name Mark Brown => Peter O'Gorman
2009-07-01 18:07 Don Cragun Organization IBM =>
2009-07-01 18:07 Don Cragun Reporter msbrown => pogma
2009-08-06 16:30 nick Note Added: 0000190
2009-08-11 16:39 Don Cragun Interp Status => Pending
2009-09-17 15:41 nick Interp Status Pending => Proposed
2009-10-12 05:50 ajosey Note Edited: 0000138
2009-10-12 05:50 ajosey Interp Status Proposed => Approved
2010-09-20 09:28 geoffclare Tag Attached: tc1-2008
2011-03-24 15:07 eblake Relationship added related to 0000075
2011-03-30 09:52 ajosey Note Added: 0000729
2013-04-16 13:06 ajosey Status Interpretation Required => Closed