From owner-freebsd-hackers Fri Jul 23 21: 6:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9086814D41 for ; Fri, 23 Jul 1999 21:06:14 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA04539 for ; Sat, 24 Jul 1999 00:05:20 -0400 (EDT) Message-Id: <199907240405.AAA04539@cs.rpi.edu> To: freebsd-hackers@freebsd.org Subject: mbuf leakage Date: Sat, 24 Jul 1999 00:05:18 -0400 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it doesn't appear to be commit() :(. Any-who, is there a way I can get a look at the raw mbuf/mbuf-clusters? I have a feeling that seeing the data in them would speak volumes of information. Preferably a way to see them without DDB/panic would be ideal. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message