Re: How do I debug kernel MEMORY LEAKS?

Bill Hawes (whawes@star.net)
Tue, 28 Oct 1997 15:43:24 -0500

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: root: "Kernels 2.1 with 386DX/387 IRQ13 PC boxes"
Previous message: Andi Gutmans: "Linux 2.0.31 went nuts"
Maybe in reply to: Brian Topping: "How do I debug kernel MEMORY LEAKS?"

Brian Topping wrote:
> I am trying to figure out how to debug a memory leak. I know what file
> the problem is coming from (a networking module that I wrote that caches
> skbuffs), but I can't tell what I did wrong. I found the
> <shift-scrollock> method of dumping the mem info. [btw, why is this
> different than the info from /proc/meminfo?]. What do the regulars do
> to get even more info about what is going on?

Memory leaks are tricky to debug! That's why there are so many of them
...

> I think I need to find good documentation (even if it is reading the
> source, at last resort) on how to treat skbuffs and the context and
^^^^^^^^^^^
Best to make this the first resort ...

Regards,
Bill

Next message: root: "Kernels 2.1 with 386DX/387 IRQ13 PC boxes"
Previous message: Andi Gutmans: "Linux 2.0.31 went nuts"
Maybe in reply to: Brian Topping: "How do I debug kernel MEMORY LEAKS?"