From owner-freebsd-hackers  Tue Sep 16 10:43:55 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA08336
          for hackers-outgoing; Tue, 16 Sep 1997 10:43:55 -0700 (PDT)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08329;
          Tue, 16 Sep 1997 10:43:50 -0700 (PDT)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id TAA01024;
	Tue, 16 Sep 1997 19:43:14 +0200 (CEST)
To: Graham Wheeler <gram@cdsec.com>
cc: freebsd-bugs@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject: Re: Memory leak in getservbyXXX? 
In-reply-to: Your message of "Sat, 16 Sep 1997 17:35:19 +0200."
             <199709161535.RAA00281@cdsec.com> 
Date: Tue, 16 Sep 1997 19:43:13 +0200
Message-ID: <1022.874431793@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In message <199709161535.RAA00281@cdsec.com>, Graham Wheeler writes:
>First off, I should say that I have found the problem. It is entirely my
>own code, so apologies for wasting people's time. Nontheless, I appreciate
>all the suggestions I got, and I learnt some useful stuff in the process
>(like the malloc options, which I never knew existed, not having done a
>`man malloc' for several years...)

Well, I found out that nobody else had either :-)

It's much against my liking that the process can spin when I call abort(),
but that is apearantly what POSIX dictates :-(

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."