IEEE Standards AssociationCopyright © 2006 IEEE. All rights reserved.
Defect Report concerning (number and title of International Standard
or DIS final text, if applicable):
Interpretation Number: 013
Topic: Defect in XSH getaddrinfo
Relevant Sections: EAI_OVERFLOW
------------------------------------------------------------------------
7 Defect Report concerning (number and title of International Standard
or DIS final text, if applicable):
The System Interfaces Volume of IEEE Std 1003.1-2001
------------------------------------------------------------------------
8 Qualifier (e.g. error, omission, clarification required):
1. Error
------------------------------------------------------------------------
9 References in document (e.g. page, clause, figure, and/or table
numbers):
Page: 426 Line: 13994-13995 Section: getaddrinfo
XSHft6 Enhancement Request Number 3
------------------------------------------------------------------------
10 Nature of defect (complete, concise explanation of the perceived
problem):
EAI_OVERFLOW is specified as a possible error value for the
getaddrinfo() function on lines 13994-13995:
13994 [EAI_OVERFLOW]
13995 An argument buffer overflowed.
The EAI_OVERFLOW error code was created to provide a meaningful
error code for the getnameinfo() function, for the case where
the buffers provided by the caller were too small.
The EAI_OVERFLOW error code is not applicable to getaddrinfo(),
which has no buffer arguments to overflow.
EAI_OVERFLOW was mistakenly added to the getaddrinfo() page
rather than the getnameinfo() page. Another aardvark has
already been approved for TC1 to add EAI_OVERFLOW to getnameinfo().
------------------------------------------------------------------------
11 Solution proposed by the submitter (optional):
Delete lines 13994-13995.
------------------------------------------------------------------------
Interpretation response
------------------------
The standard states that EAI_OVERFLOW is a possible error
and conforming implementations must
conform to this. However, concerns have been raised about this
which are being referred to the sponsor
Rationale:
-------------
None.
_____________________________________________________________________________
Back to IEEE Standards Interpretations for IEEE Std 1003.1-2001