Xref: utzoo comp.unix.wizards:9788 comp.protocols.tcp-ip:4036
Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!ames!amdahl!pyramid!prls!philabs!ttidca!mb
From: mb@ttidca.TTI.COM (Michael Bloom)
Newsgroups: comp.unix.wizards,comp.protocols.tcp-ip
Subject: Re: mbuf leaks
Message-ID: <2882@ttidca.TTI.COM>
Date: 9 Jul 88 12:18:26 GMT
References: <2881@ttidca.TTI.COM>
Reply-To: mb@ttidca.tti.com (Michael Bloom)
Organization: Citicorp/TTI, Santa Monica
Lines: 16

A couple of hours ago, in article <2881@ttidca.TTI.COM> I wrote:
>	Can anyone suggest good techniques for tracking down mbuf leaks?

The problem was simple: turned out to be an "m_free" where there
should have been an "m_freem". While unneeded at present, i'd still be
interested in learning of other peoples network debugging techniques.

A new question: Has anyone tried rewriting the mbuf allocation
routines and macros to internally use streams data structures? This
looks like it might be a workable approach to converting the BSD TCP
to streams, without having to change too much of the rest of the code.

If I can find out soon enough whether or not s5r4 tcp will be streams
based, I may end up doing such a conversion to get a head start prior
to r4 availability.  I know I've asked this before, but I've gotten no
replies: does anyone know if this will be the case?