Date: Sun, 6 Apr 1997 01:44:17 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: chadf@bookcase.com (Chad M. Fraleigh) Cc: msmith@atrad.adelaide.edu.au, hackers@FreeBSD.ORG Subject: Re: Code maintenance Message-ID: <199704051614.BAA27630@genesis.atrad.adelaide.edu.au> In-Reply-To: <Pine.BSF.3.95.970405105614.21030A-100000@notes> from "Chad M. Fraleigh" at "Apr 5, 97 11:05:53 am"
next in thread | previous in thread | raw e-mail | index | archive | help
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 [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704051614.BAA27630>