Re: BUG: getaddrinfo(3) mentions errors that are only exposed via `_GNU_SOURCE` preprocessor constant, e.g., `ENODATA`

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello Enji,

On 3/2/19 9:18 PM, Enji Cooper (yaneurabeya) wrote:
> Hello!
> I’ve been working with the libevent team trying to reconcile
> `_GNU_SOURCE` pollution [1] in their library, and (as was pointed out
> to me in a pull request [2], [3]) some errors returned by
> `getaddrinfo(3)` in the Linux manpage lead the end-user to think that
> they are available in non-`GNU_SOURCE` cases, i.e., more POSIX
> compliant modes, when in reality they’re not, leading to some really
> potentially confusing error handling [4].
> While I suspect that this doesn’t affect the behavior of glibc, it
> most definitely affects the expectations for callers, which the man
> page documents.
>
> Please advise how you’d like to proceed. I will submit patches via
> `git format-patch` once I understand the general direction I need to
> implement the fix.
I'm happy to take patches to fix this. Just write a patch :-).

Cheers,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/



[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux