From owner-freebsd-net@FreeBSD.ORG Tue Sep 21 23:45:01 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E24116A4CE; Tue, 21 Sep 2004 23:45:01 +0000 (GMT) Received: from outbound0.sv.meer.net (outbound0.sv.meer.net [205.217.152.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0768443D1D; Tue, 21 Sep 2004 23:45:01 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from mail.meer.net (mail.meer.net [209.157.152.14]) i8LNiKr6099452; Tue, 21 Sep 2004 16:44:23 -0700 (PDT) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (pc1.oakwoodazabu1-unet.ocn.ne.jp [220.110.140.201]) by mail.meer.net (8.12.1/8.12.2/meer) with ESMTP id i8LNi3lS011986; Tue, 21 Sep 2004 16:44:03 -0700 (PDT) (envelope-from gnn@neville-neil.com) Date: Wed, 22 Sep 2004 08:44:01 +0900 Message-ID: From: "George V. Neville-Neil" To: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= In-Reply-To: References: <20040921123016.GA41677@melusine.cuivre.fr.eu.org> <20040921190717.GG84228@lucky.net> <20040921213233.GA84392@melusine.cuivre.fr.eu.org> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.5 Emacs/21.2 (powerpc-apple-darwin) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=ISO-2022-JP cc: netch@lucky.net cc: freebsd-net@freebsd.org cc: Hajimu UMEMOTO cc: Thomas Quinot Subject: Re: freeaddrinfo(NULL) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Sep 2004 23:45:01 -0000 At Wed, 22 Sep 2004 07:37:20 +0900, JINMEI Tatuya / 神明達哉 wrote: > Note also that other *BSDs and Solaris use the "segfault" logic. The > freeaddrinfo implementation in the "libbind" library as a part of the > ISC BIND package, which many UNIX-like OS vendors adopt (perhaps with > vendor-specific modifications though), also segfaults against a NULL > argument. > > So, although consistency might in general be a good thing, the real > world's examples show we just have variations. > Sorry to come in late on this, but you know I was asleep. One quick comment. It is easier to find and fix the bug that relating to a NULL pointer if the program seg faults than if it continues blithely on. I think we should stick with failing early. Later, George