status of kernel memory debugging?

hi all,

For a project in packet filtering (ffpf.sf.net) I'm in the process of 
debugging kernel code I wrote. I have the habit of running all userspace code 
through valgrind, and have setup user-mode-linux to do the same with the 
kernel. 

Reading through some old LKML threads I see that there has been talk of 
valgrinding a UML image, but the outcome appears inconclusive. Could someone 
please update me on the status of memory debugging in the kernel, especially 
regarding valgrind?

Do you have other tools you regularly use, or is is simply a trial-and-error 
practice? Note that I already export my kernelspace code to userspace for 
unit-testing where possible. It is only in the ioctl/syscall handlers that 
this technique fails.

thanks,

  Willem de Bruijn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: status of kernel memory debugging?
    • From: Jeff Dike <[email protected]>

• Prev by Date: Re: [patch 2.6.13-rc3] sis190 driver
• Next by Date: Re: [patch 2.6.13-rc3] sis190 driver
• Previous by thread: local_irq_enable() in __do_softirq()?
• Next by thread: Re: status of kernel memory debugging?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]