Re: 1.7.0: getnameinfo bug

2009-08-06 Thread Mark J. Reed
On Thu, Aug 6, 2009 at 9:12 AM, Corinna Vinschen wrote: > On Aug  6 09:01, Mark J. Reed wrote: >> According to the RFC (2553), the specific behavior here is not defined: > Microsoft's getnameinfo man page conveniently notes that this is the desired > behaviour according to section 6.2 of RFC 3493

Re: 1.7.0: getnameinfo bug

2009-08-06 Thread Corinna Vinschen
On Aug 6 09:01, Mark J. Reed wrote: > On Thu, Aug 6, 2009 at 8:48 AM, Zhiming Zhou wrote: > > This bug happens on every 1.7.0 beta version. > > I use getnameinfo function with NI_NUMERICHOST flag, > > I assume that it works if you pass NI_NUMERICSERV (returning e.g. "21" > instead of "ftp" in tha

Re: 1.7.0: getnameinfo bug

2009-08-06 Thread Corinna Vinschen
On Aug 6 20:48, Zhiming Zhou wrote: > This bug happens on every 1.7.0 beta version. > I use getnameinfo function with NI_NUMERICHOST flag, > > if the "sin_port" of sockaddr is a known port(like 21, 80...) > in "/etc/services" file, getnameinfo function works ok, and > service name is correctly fe

Re: 1.7.0: getnameinfo bug

2009-08-06 Thread Mark J. Reed
On Thu, Aug 6, 2009 at 8:48 AM, Zhiming Zhou wrote: > This bug happens on every 1.7.0 beta version. > I use getnameinfo function with NI_NUMERICHOST flag, I assume that it works if you pass NI_NUMERICSERV (returning e.g. "21" instead of "ftp" in that case). According to the RFC (2553), the specif

1.7.0: getnameinfo bug

2009-08-06 Thread Zhiming Zhou
This bug happens on every 1.7.0 beta version. I use getnameinfo function with NI_NUMERICHOST flag, if the "sin_port" of sockaddr is a known port(like 21, 80...) in "/etc/services" file, getnameinfo function works ok, and service name is correctly fetched(ftp, http...). however if I fill "sin_port