Hajimu UMEMOTO ume at
Tue Sep 21 10:31:01 PDT 2004


>>>>> On Tue, 21 Sep 2004 14:30:16 +0200
>>>>> Thomas Quinot <thomas at FreeBSD.ORG> said:

thomas> Currently a call to freeaddrinfo (NULL) causes a segfault. Is there any
thomas> reason why we should not make that a no-op? This would make freeaddrinfo
thomas> behave in a manner consistent with free(3), and also with what happens
thomas> on Linux.

Because, the behavior of freeaddrinfo (NULL) is undefined in RFC 2553
nor RFC 3493.  Having such an assumption is a potentially bug and
lose portability.


Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume at  ume@{,jp.}

More information about the freebsd-net mailing list