From owner-freebsd-bugs  Tue Sep 16 22:25:47 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA16661
          for bugs-outgoing; Tue, 16 Sep 1997 22:25:47 -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 WAA16653
          for <freebsd-bugs@FreeBSD.ORG>; Tue, 16 Sep 1997 22:25:43 -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 HAA07155;
	Wed, 17 Sep 1997 07:25:07 +0200 (CEST)
To: Mike Smith <mike@smith.net.au>
cc: Graham Wheeler <gram@cdsec.com>, freebsd-bugs@FreeBSD.ORG
Subject: Re: Memory leak in getservbyXXX? 
In-reply-to: Your message of "Wed, 17 Sep 1997 09:08:16 +0930."
             <199709162338.JAA00286@word.smith.net.au> 
Date: Wed, 17 Sep 1997 07:25:06 +0200
Message-ID: <7153.874473906@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In message <199709162338.JAA00286@word.smith.net.au>, Mike Smith writes:
>>  
>> The only syscalls/libs called from phkmalloc are sbrk(), write(), 
>> madvise(), mmap(), and abort().  At least as far as I remember.
>
>There's a readlink() in there as well,

Ahh, yes, forgot that.

>Would building malloc with EXTRA_SANITY help if there is indeed a 
>corruption issue involved?

I doubt it.

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