From: Willem de Bruijn <wdb@few.vu.nl>
To: Jeff Dike <jdike@addtoit.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: status of kernel memory debugging?
Date: Sat, 30 Jul 2005 23:12:06 +0200 [thread overview]
Message-ID: <200507302312.09384.wdb@few.vu.nl> (raw)
In-Reply-To: <20050730151432.GA3524@ccure.user-mode-linux.org>
> 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.
>
I think I read your remark, yes. Thanks for the update; I hoped some strides
had been made in that direction since then. Personally, I know to little
about the topic to be of any use.
I guess the best option is then using slab caches per object type, so that I
can at least find obvious memory leaks.
On a sidenote, it'll be interesting to see what valgrind reports once (if?)
the kernel gets a good grinding.
Willem
prev parent reply other threads:[~2005-07-30 21:12 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
2005-07-30 21:12 ` Willem de Bruijn [this message]
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=200507302312.09384.wdb@few.vu.nl \
--to=wdb@few.vu.nl \
--cc=jdike@addtoit.com \
--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 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.