Daniele ... please do pass on the tutorial. On the web we get a lot of stuff, but if you have something nice I will not have to search it out. thanks Deepankar. On Thu, 2003-06-12 at 15:15, Daniele Bellucci wrote: > On Thu 12 June 2003 11:38, Deepankar Vidyarthi wrote: > > Hi, > > > > I have written a kernel module. But it seems this guy is corrupting > > memory somewhere because of which I get kernel segmentation and then > > panic. > > > > I tried looking into the problem using kgdb, but I am not getting proper > > information regarding where the problem is arising from. The code seems > > alright (which is always the case for the person who writes it ;)). > > > > I wanted to know whether there are any ways (tools, etc) to catch memory > > leaks or memory corruption for kernel modules. > > > > TIA, > > Deepankar. > > I had the same problem months ago.... i've solved by using ksymoops to examine call trace before oops occour. > I didn't used kgdb, i've just played with kcore, gdb and a -g kernel image. > If you have trouble on finding the oopsy line in source code, feel free to contact > i've a little tutorial showing some usefull tricks to match ksymoops output with source code (both for source kernel and device driver). > > > > > Daniele. > > > PGP PKEY http://pgp.mit.edu:11371/pks/lookup?search=belch76@libero.it&op=index > ICQ# 104896040 > Netphone/Fax 178.605.7063 > Homepage http://web.tiscali.it/bellucda > > > > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
