Re: freeaddrinfo(NULL)

From: Thomas Quinot (thomas_at_FreeBSD.ORG)
Date: 09/21/04

  • Next message: Brooks Davis: "Re: freeaddrinfo(NULL)" 
    Date: Tue, 21 Sep 2004 20:07:46 +0200
To: Hajimu UMEMOTO <ume@FreeBSD.org>

    * Hajimu UMEMOTO, 2004-09-21 :

    > 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.

    That a construct has no defined meaning does not imply that we must make
    every effort to break applications that (erroneously) make use of it.
    Would there be any significant drawback for conforming applications
    if we made our best to deploy a safety net againt buggy user programs
    by not segfaulting in this case?

    There are many situations where the system already detects an invalid
    pointer and reports it gracefully as an error rather than triggering a
    fatal signal.

    Thomas. 

    -- 
    Thomas.Quinot@Cuivre.FR.EU.ORG
_______________________________________________
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"
  • Next message: Brooks Davis: "Re: freeaddrinfo(NULL)"