Messages in this thread | | | Date | Mon, 29 Jun 2009 14:08:12 +0300 | From | Sergey Senozhatsky <> | Subject | Re: kmemleak hexdump proposal |
| |
On (06/29/09 11:58), Catalin Marinas wrote: > On Mon, 2009-06-29 at 13:45 +0300, Sergey Senozhatsky wrote: > > BTW, printing it all the time we can spam kmemleak (in case there are objects sized 2K, 4K and so on). > > That's why I wrote about hexdump=OBJECT_POINTER. > > I'm more in favour of an on/off hexdump feature (maybe even permanently > on) and with a limit to the number of bytes it displays. For larger > blocks, the hexdump=OBJECT_POINTER is easily achievable in user space > via /dev/kmem. > Yeah. Good point.
> My proposal is for an always on hexdump but with no more than 2-3 lines > of hex values. I like it.
> As Pekka said, I should get it into linux-next before the > next merging window. I'll send new patch to you (today evening)/(tomorrow). Ok?
> > -- > Catalin >
Sergey
| |