From owner-freebsd-hackers Sat Apr 5 08:14:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA15022 for hackers-outgoing; Sat, 5 Apr 1997 08:14:34 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA15016 for ; Sat, 5 Apr 1997 08:14:29 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id BAA27630; Sun, 6 Apr 1997 01:44:18 +0930 (CST) From: Michael Smith Message-Id: <199704051614.BAA27630@genesis.atrad.adelaide.edu.au> Subject: Re: Code maintenance In-Reply-To: from "Chad M. Fraleigh" at "Apr 5, 97 11:05:53 am" To: chadf@bookcase.com (Chad M. Fraleigh) Date: Sun, 6 Apr 1997 01:44:17 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Chad M. Fraleigh stands accused of saying: > > > > 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). Hmm, nasty. You could add an extra field to the memory block header with the address of the caller in it, which would help a lot. (With that you could nominate caller and possibly line number, but a full backtrace for every block is a big ask). > -Chad -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[