Messages in this thread | | | From | Willem de Bruijn <> | Subject | status of kernel memory debugging? | Date | Sat, 30 Jul 2005 13:23:27 +0200 |
| |
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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |