From owner-freebsd-hackers  Sat Apr  5 08:02:27 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA14063
          for hackers-outgoing; Sat, 5 Apr 1997 08:02:27 -0800 (PST)
Received: from bookcase.com (root@notes.bookcase.com [207.22.115.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA14058
          for <hackers@FreeBSD.ORG>; Sat, 5 Apr 1997 08:02:23 -0800 (PST)
Received: from localhost (chadf@localhost) by bookcase.com (8.8.5/8.7.3) with SMTP id KAA21060; Sat, 5 Apr 1997 10:05:54 -0500 (EST)
Date: Sat, 5 Apr 1997 11:05:53 -0400 (EST)
From: "Chad M. Fraleigh" <chadf@bookcase.com>
X-Sender: chadf@notes
To: Michael Smith <msmith@atrad.adelaide.edu.au>
cc: hackers@FreeBSD.ORG
Subject: Re: Code maintenance
In-Reply-To: <199704050505.OAA26477@genesis.atrad.adelaide.edu.au>
Message-ID: <Pine.BSF.3.95.970405105614.21030A-100000@notes>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


> > 	Anyway.. now I'm working on a way to trace kernel memory leaks.
> 
> 'vmstat -m' is your friend!

	That seems somewhat useful, but I was thinking along the lines of
exact details.. like what function the memory was allocated it (stack
backtrace). Perhaps even to the source line number (assuming the -g kernel
info was avaliable).


-Chad