From owner-freebsd-net@FreeBSD.ORG  Tue Sep 21 12:30:18 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
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 DBA4B16A4CE
	for <freebsd-net@freebsd.org>; Tue, 21 Sep 2004 12:30:18 +0000 (GMT)
Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org
	[82.225.155.84])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7FEAD43D2F
	for <freebsd-net@freebsd.org>; Tue, 21 Sep 2004 12:30:18 +0000 (GMT)
	(envelope-from thomas@FreeBSD.ORG)
Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000)
	id 531632C3D0; Tue, 21 Sep 2004 14:30:16 +0200 (CEST)
Date: Tue, 21 Sep 2004 14:30:16 +0200
From: Thomas Quinot <thomas@FreeBSD.ORG>
To: freebsd-net@freebsd.org
Message-ID: <20040921123016.GA41677@melusine.cuivre.fr.eu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-message-flag: WARNING! Using Outlook can damage your computer.
User-Agent: Mutt/1.5.6i
Subject: freeaddrinfo(NULL)
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Sep 2004 12:30:19 -0000

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

Thomas.

-- 
    Thomas.Quinot@Cuivre.FR.EU.ORG