Re: freeaddrinfo(NULL)
From: Hajimu UMEMOTO (ume_at_FreeBSD.org)
Date: 09/21/04
- Previous message: Brooks Davis: "Re: Global (non _KERNEL) place for sockaddr_union?"
- In reply to: Thomas Quinot: "freeaddrinfo(NULL)"
- Next in thread: Thomas Quinot: "Re: freeaddrinfo(NULL)"
- Reply: Thomas Quinot: "Re: freeaddrinfo(NULL)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 22 Sep 2004 02:30:54 +0900 To: Thomas Quinot <thomas@FreeBSD.ORG>
Hi,
>>>>> On Tue, 21 Sep 2004 14:30:16 +0200
>>>>> Thomas Quinot <thomas@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.
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
- Previous message: Brooks Davis: "Re: Global (non _KERNEL) place for sockaddr_union?"
- In reply to: Thomas Quinot: "freeaddrinfo(NULL)"
- Next in thread: Thomas Quinot: "Re: freeaddrinfo(NULL)"
- Reply: Thomas Quinot: "Re: freeaddrinfo(NULL)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]