From: Willem de Bruijn <wdb@few.vu.nl>
To: linux-kernel@vger.kernel.org
Subject: status of kernel memory debugging?
Date: Sat, 30 Jul 2005 13:23:27 +0200 [thread overview]
Message-ID: <200507301323.28083.wdb@few.vu.nl> (raw)
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
next reply other threads:[~2005-07-30 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 11:23 Willem de Bruijn [this message]
2005-07-30 15:14 ` status of kernel memory debugging? Jeff Dike
2005-07-30 21:12 ` Willem de Bruijn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200507301323.28083.wdb@few.vu.nl \
--to=wdb@few.vu.nl \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox