This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug network/15726] getaddrinfo() returns incorrect status
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 18 Jul 2013 07:03:09 +0000
- Subject: [Bug network/15726] getaddrinfo() returns incorrect status
- Auto-submitted: auto-generated
- References: <bug-15726-131 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15726
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #13 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Rich Felker from comment #12)
> Conceptually, this whole topic is very simple. getaddrinfo has two
> "successful" result possibilities, 0 and EAI_NONAME.
>
> 0 means a successful query was performed and returned a result.
>
> EAI_NONAME means a successful query was performed and determined that the
> queried name does not (by hostname lookup) or cannot (by virtue of being an
> invalid ip string) exist.
>
> All other result codes indicate to the application that something went wrong
> during the name resolving process, and that the result is indeterminate.
What about EAI_NODATA which glibc still uses? It would seem that EAI_NODATA is
more likely be returned in the current implementation than EAI_NONAME (which is
mostly returned for the parameter errors discussed).
--
You are receiving this mail because:
You are on the CC list for the bug.