Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Debugging the Memory leakage

2 views
Skip to first unread message

Anand

unread,
Jan 31, 2006, 4:06:47 AM1/31/06
to
Hi All
Can any one help me knowing how to debug the memory leakage in linux
kernel.

Thanks In Advance
Anand

Kasper Dupont

unread,
Jan 31, 2006, 6:05:44 AM1/31/06
to
Anand wrote:
>
> Hi All
> Can any one help me knowing how to debug the memory leakage in linux
> kernel.

Does this information help you?
http://www.daimi.au.dk/~kasperd/comp.os.linux.development.faq.html#memleak

--
Kasper Dupont -- Rigtige mænd skriver deres egne backupprogrammer
#define _(_)"d.%.4s%."_"2s" /* This is my new email address */
char*_="@2kaspner"_()"%03"_("4s%.")"t\n";printf(_+11,_+6,_,6,_+2,_+7,_+6);

Peter T. Breuer

unread,
Jan 31, 2006, 6:26:13 AM1/31/06
to
Kasper Dupont <2442915126...@expires.14.mar.2006.kasperd.net.invalid> wrote:

> Anand wrote:
>> Can any one help me knowing how to debug the memory leakage in linux
>> kernel.

> Does this information help you?
> http://www.daimi.au.dk/~kasperd/comp.os.linux.development.faq.html#memleak

That's ridiculously helpful.

But it ignores the fact that all that leaking memory must be going
somewhere. Look for soggy patches under the cpu on the case. Bits have
a positive dielectric constant which reacts with the negative ions in
the lattice of crystalline microzones in the aluminium alloy in the case.
Loking along the light you should be able to see something amiss if it
is a regularly recurring problem.

Other people will give you silly advice on occasions - follow your own
feelings on the matter. If you suspect that something is stealing away
precious memory, it likely is so. In my experience, the surest course
is usually to take time out to grow a kid brother who is smarter than
you. You can trust what family say.

And if you get a jury service note for the RIAA case, accept.

(:Peter:)

Peter T. Breuer

unread,
Jan 31, 2006, 6:37:07 AM1/31/06
to
Kasper Dupont <2442915126...@expires.14.mar.2006.kasperd.net.invalid> wrote:
> http://www.daimi.au.dk/~kasperd/comp.os.linux.development.faq.html#memleak

Nice text.

Doesn't mention my favorite memory debugger technique, however:

dmalloc - Debug memory allocation library

Things like valgrind and electric-fence are too heavyweight for my
taste. Dmalloc just links in a new malloc library.

Peter

Kasper Dupont

unread,
Jan 31, 2006, 6:50:49 AM1/31/06
to
"Peter T. Breuer" wrote:
>
> Kasper Dupont <2442915126...@expires.14.mar.2006.kasperd.net.invalid> wrote:
> > http://www.daimi.au.dk/~kasperd/comp.os.linux.development.faq.html#memleak
>
> Nice text.
>
> Doesn't mention my favorite memory debugger technique, however:
>
> dmalloc - Debug memory allocation library

The FAQ entry was about kernel memory leaks. But maybe I should
include a list of memory leak debuging utilities for kernel and
user space. Are there other utilities which should be included
in such a list?

milind....@gmail.com

unread,
Jan 31, 2006, 7:37:35 AM1/31/06
to
Use KGDB.

Kasper Dupont

unread,
Jan 31, 2006, 7:53:02 AM1/31/06
to
milind....@gmail.com wrote:
>
> Use KGDB.

Do you have links with more information?

Anand

unread,
Feb 1, 2006, 3:18:55 AM2/1/06
to
No Idon't have, can help me by giving the information,

Thanks & Regards
Anand

Sagar Borikar

unread,
Feb 1, 2006, 3:52:32 AM2/1/06
to

Kasper Dupont wrote:

> Do you have links with more information?

mpatrol will help you

http://www.cbmamiga.demon.co.uk/mpatrol/


Regards,
Sagar

0 new messages