openbsd/src/lib/libc/net/freeaddrinfo.c, branch OPENBSD_4_2_BASE A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_4_2_BASE 2005-03-25T13:24:12+00:00 ansify. ok deraadt@ moritz@ 2005-03-25T13:24:12+00:00 otto 2005-03-25T13:24:12+00:00 urn:sha1:2f490723a2e673b2457f65c4b06cacb7d700a3e8 add some missing $, ok djm@ 'That looks fine to me' millert@ 2004-10-01T04:08:45+00:00 jsg 2004-10-01T04:08:45+00:00 urn:sha1:286f2c9acc73fa2c79290ce6e5c7437d99f9f865 don't permit freeaddrinfo(NULL). now the behavior is consistent 2000-01-28T17:47:26+00:00 itojun 2000-01-28T17:47:26+00:00 urn:sha1:af545fafa6ab3bf7a4f91cc73e97df4db15930c1 across {free,net,open}bsd. both rfc2553 and X/Open spec are silent about the behavior, and there's no strong consensus either. i think library should NOT be forgiving in this case, to promote development of more robust 3rd-party codebase (code works on "freeaddrinfo(NULL) = SEGV" will work on "freeaddrinfo(NULL) is okay" environment, but not the other way around). only issue i have now is NRL freeaddrinfo() compatibility, which permits freeaddrinfo(NULL). avoid memory leakage on freeaddrinfo(). 2000-01-27T08:23:46+00:00 itojun 2000-01-27T08:23:46+00:00 urn:sha1:5b1f731bf4378d5cde8894a5aa27c652e69e5a5f (this bug was introduced since we mix KAME getaddrinfo and NRL freeaddrinfo). KNF 1999-06-23T22:14:51+00:00 deraadt 1999-06-23T22:14:51+00:00 urn:sha1:c9acd185820380c6eedba713cb86eaf97af03d53 Added some protocol independent interfaces (supposedly IPv6 support APIs, but 1999-06-23T21:55:29+00:00 cmetz 1999-06-23T21:55:29+00:00 urn:sha1:bdf7624d67f3bba1a3faed9abf0d2d27291c1cce ones that are useful for all protocols, not just IPv6).