From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GwEIK-0008DO-Qk
	for qemu-devel@nongnu.org; Mon, 18 Dec 2006 03:56:24 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GwEIJ-0008Aj-1k
	for qemu-devel@nongnu.org; Mon, 18 Dec 2006 03:56:24 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GwEII-0008AQ-TM
	for qemu-devel@nongnu.org; Mon, 18 Dec 2006 03:56:22 -0500
Received: from [66.249.92.175] (helo=ug-out-1314.google.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1GwEII-0006dT-Vt
	for qemu-devel@nongnu.org; Mon, 18 Dec 2006 03:56:23 -0500
Received: by ug-out-1314.google.com with SMTP id j40so1359361ugd
	for <qemu-devel@nongnu.org>; Mon, 18 Dec 2006 00:56:21 -0800 (PST)
Message-ID: <891be9410612180056j48be1981v2a62a4668f9da050@mail.gmail.com>
Date: Mon, 18 Dec 2006 00:56:19 -0800
From: "Diwaker Gupta" <diwaker.lists@gmail.com>
Subject: Re: [Qemu-devel] Tracing guest memory accesses
In-Reply-To: <1166356376.4186.3.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <891be9410612161942t28116f7w12123ebca0ca6278@mail.gmail.com>
	<20061217035307.GA32712@nevyn.them.org>
	<891be9410612162319o7828c31ehc3bcf986a3ea991e@mail.gmail.com>
	<1166356376.4186.3.camel@localhost.localdomain>
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

> as far as i remember i had to put the same code into softmmu_header.h to
> get "correct" results.
> i found it easiest to do this in the ld/st macros in these files (~6
> places in code)

This probably sounds stupid but whats the best way to get debug
output? Due to the code generation magic qemu does, simply adding
printfs doesn't seem to work well. In particular, all my attempts to
add printfs to softmmu_header.h have resulted in broken builds. Are
there any global macros I should be using?

Thanks,
Diwaker
-- 
Web/Blog/Gallery: http://floatingsun.net/blog