From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1CVicj-0007U4-G8
	for qemu-devel@nongnu.org; Sat, 20 Nov 2004 22:42:49 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1CVici-0007Tb-M6
	for qemu-devel@nongnu.org; Sat, 20 Nov 2004 22:42:48 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1CVici-0007TG-GB
	for qemu-devel@nongnu.org; Sat, 20 Nov 2004 22:42:48 -0500
Received: from [128.112.136.38] (helo=bluebox.CS.Princeton.EDU)
	by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168)
	(Exim 4.34) id 1CViT9-0005qV-64
	for qemu-devel@nongnu.org; Sat, 20 Nov 2004 22:32:55 -0500
Received: from localhost.localdomain (pcp09895218pcs.ewndsr01.nj.comcast.net
	[68.36.161.67]) (authenticated bits=0)
	by bluebox.CS.Princeton.EDU (8.12.11/8.12.11) with ESMTP id
	iAL3WppV019285
	(version=TLSv1/SSLv3 cipher=EXP-RC4-MD5 bits=40 verify=NOT)
	for <qemu-devel@nongnu.org>; Sat, 20 Nov 2004 22:32:53 -0500 (EST)
From: "Marc E. Fiuczynski" <mef@CS.Princeton.EDU>
Date: Sat, 20 Nov 2004 22:32:52 -0500
Message-ID: <NIBBJLJFDHPDIBEEKKLPKEENCMAA.mef@cs.princeton.edu>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <200411210320.57165.jseward@acm.org>
Subject: [Qemu-devel] valgrind functionality in qemu?
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

Just curious whether anyone has thought about putting things like the =
memory profiling, thread debugging, etc. features of valgrind =
(http://valgrind.kde.org/) into qemu?!  It sure would be AWESOME to use =
qemu to hunt down memory bugs in kernels and/or perform cache profiling =
to optimize layout of data structures.=20

Marc