Messages in this thread | | | Subject | Re: kmemleak hexdump proposal | From | Catalin Marinas <> | Date | Mon, 29 Jun 2009 10:48:42 +0100 |
| |
On Mon, 2009-06-29 at 12:43 +0300, Pekka Enberg wrote: > On Sun, Jun 28, 2009 at 8:36 PM, Sergey > Senozhatsky<sergey.senozhatsky@mail.by> wrote: > > What do you think about ability to 'watch' leaked region? (hex + ascii). > > (done via lib/hexdump.c) > > What's your use case for this? I'm usually more interested in the > stack trace when there's a memory leak.
I once had a need for such feature when investigating a memory leak (it was more like debugging kmemleak) but a script combining dd, od and /dev/kmem did the trick (I also work in an embedded world where I have a halting debugger connected most of the times).
-- Catalin
| |