From owner-freebsd-hackers  Thu Sep 18 16:44:41 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA18154
          for hackers-outgoing; Thu, 18 Sep 1997 16:44:41 -0700 (PDT)
Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA18147
          for <hackers@freebsd.org>; Thu, 18 Sep 1997 16:44:37 -0700 (PDT)
Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100])
	by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id RAA10837;
	Thu, 18 Sep 1997 17:40:44 -0600 (MDT)
Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id RAA15292; Thu, 18 Sep 1997 17:40:43 -0600 (MDT)
Date: Thu, 18 Sep 1997 17:40:43 -0600 (MDT)
Message-Id: <199709182340.RAA15292@rocky.mt.sri.com>
From: Nate Williams <nate@mt.sri.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Terry Lambert <tlambert@primenet.com>
Cc: nate@mt.sri.com (Nate Williams), phk@critter.freebsd.dk, gram@cdsec.com,
        hackers@freebsd.org
Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?)
In-Reply-To: <199709182207.PAA17437@usr03.primenet.com>
References: <199709182146.PAA14637@rocky.mt.sri.com>
	<199709182207.PAA17437@usr03.primenet.com>
X-Mailer: VM 6.29 under 19.15 XEmacs Lucid
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > > Now you must find the length of the loop.  You save the current
> > > pointer, and traverse until you see it again, counting.  This count
> > > is the length of the loop.
..
> The point is to detect the addresses of the objects which when
> manipulated resulted in the loop in the first place.  Without
> that information, you;ll only know you have a loop.  Big deal, I
> can tell I have a loop when it hangs in malloc() forever.  8-).

Ahh, at this point you dump core, and then the debugger can be used to
go look at malloc's lists.


Nate