From: Jeff Dike <jdike@addtoit.com>
To: Willem de Bruijn <wdb@few.vu.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: status of kernel memory debugging?
Date: Sat, 30 Jul 2005 11:14:32 -0400 [thread overview]
Message-ID: <20050730151432.GA3524@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200507301323.28083.wdb@few.vu.nl>
On Sat, Jul 30, 2005 at 01:23:27PM +0200, Willem de Bruijn wrote:
> 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?
UML is still too strange for valgrind, despite progress on both sides
(valgrind accepting more strange things and UML becoming less
strange).
I tried grinding UML a month or so ago, and its use of clone was a
sticking point.
Jeff
next prev parent reply other threads:[~2005-07-30 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 11:23 status of kernel memory debugging? Willem de Bruijn
2005-07-30 15:14 ` Jeff Dike [this message]
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=20050730151432.GA3524@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wdb@few.vu.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.