Defect in XSH pthread_attr_getstackaddr

[yyyyyy@xxxxxxxxxxxxx]

        Defect report from : Andrew Josey , The Open Group

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 998 line 31756 section pthread_attr_getstackaddr comment 
{pthread_attr_init.test.1}

Problem:

Edition of Specification (Year): 2003

Defect code :  3. Clarification required

There appears to be differing behavior amongst implementations
for what happens on the following call sequence:

        rval = pthread_attr_init( &attr );
           ...
        rval = pthread_attr_getstackaddr( &attr, &addr );

The description of pthread_attr_init states: 
"The pthread_attr_init() function shall initialize a thread attributes
object attr with the default value for all of the individual attributes
used by a given implementation."

On many implementations the call to pthread_attr_getstackaddr() succeeds. 

One implementation we have recently come up against 
returns rval == EINVAL for this case and will only succeed
if there has been a prior call to pthread_attr_setstackaddr().
(1)Is this alternative behavior conforming?

(2)If conforming, is the use of EINVAL appropriate given that TC2 
has added an EINVAL for invalid attributes and the attributes in this
case are valid due to the prior call to pthread_attr_init().



Action:

If the behavior is deemed conforming,consider revising the wording 
to note that a call to pthread_attr_getstackaddr() may fail without
a prior call to pthread_attr_setstackaddr() and add an appropriate
error condition.