Date: Thu, 18 Sep 1997 17:40:43 -0600 (MDT) From: Nate Williams <nate@mt.sri.com> 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?) Message-ID: <199709182340.RAA15292@rocky.mt.sri.com> In-Reply-To: <199709182207.PAA17437@usr03.primenet.com> References: <199709182146.PAA14637@rocky.mt.sri.com> <199709182207.PAA17437@usr03.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709182340.RAA15292>