From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F3SGG-0005XL-0I for qemu-devel@nongnu.org; Mon, 30 Jan 2006 01:11:36 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F3SGE-0005X9-9k for qemu-devel@nongnu.org; Mon, 30 Jan 2006 01:11:35 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F3SGE-0005X6-7n for qemu-devel@nongnu.org; Mon, 30 Jan 2006 01:11:34 -0500 Received: from [206.124.138.239] (helo=pdx.silverbeach.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F3SEU-0001bx-2f for qemu-devel@nongnu.org; Mon, 30 Jan 2006 01:09:46 -0500 Received: from [10.206.1.17] (tlingit.sea.silverbeach.net [10.206.1.17]) by pdx.silverbeach.net (Postfix) with ESMTP id 57E501BF2AF for ; Sun, 29 Jan 2006 22:08:28 -0800 (PST) From: Kyle Hayes Subject: Re: [Qemu-devel] Idea: Qemu as test coverage tool for kernels Date: Sun, 29 Jan 2006 22:08:26 -0800 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601292208.26827.kyle@silverbeach.net> Reply-To: kyle@silverbeach.net, qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Saturday 28 January 2006 04:26, Blue Swirl wrote: > Hi, > > Qemu's system emulators could be modified to output information about > the code areas which have been executed by the virtual CPU. The output > could then be used in standard test coverage tools. The benefit would be > the ability to get kernel-level coverage data. You might want to look a valgrind. The KDE project uses it heavily for memory leak and other types of problem detection. It is a sort of intermediate step between an interpreter and Qemu. I'm not sure where it lives, but Google should find it. Best, Kyle