From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1GwOUN-0001tD-D3 for qemu-devel@nongnu.org; Mon, 18 Dec 2006 14:49:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1GwOUL-0001qr-Du for qemu-devel@nongnu.org; Mon, 18 Dec 2006 14:49:30 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GwOUL-0001qe-5k for qemu-devel@nongnu.org; Mon, 18 Dec 2006 14:49:29 -0500 Received: from [195.3.96.102] (helo=email.aon.at) by monty-python.gnu.org with esmtp (Exim 4.52) id 1GwOUK-0007Qp-Ra for qemu-devel@nongnu.org; Mon, 18 Dec 2006 14:49:29 -0500 Received: from m730p013.adsl.highway.telekom.at (HELO [192.168.1.4]) ([62.47.251.45]) (envelope-sender ) by smarthub71.highway.telekom.at (qmail-ldap-1.03) with SMTP for ; 18 Dec 2006 19:49:26 -0000 Subject: Re: [Qemu-devel] Tracing guest memory accesses From: maestro In-Reply-To: <891be9410612180056j48be1981v2a62a4668f9da050@mail.gmail.com> References: <891be9410612161942t28116f7w12123ebca0ca6278@mail.gmail.com> <20061217035307.GA32712@nevyn.them.org> <891be9410612162319o7828c31ehc3bcf986a3ea991e@mail.gmail.com> <1166356376.4186.3.camel@localhost.localdomain> <891be9410612180056j48be1981v2a62a4668f9da050@mail.gmail.com> Content-Type: text/plain Date: Mon, 18 Dec 2006 20:49:25 +0100 Message-Id: <1166471365.4186.17.camel@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Reply-To: 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 Am Montag, den 18.12.2006, 00:56 -0800 schrieb Diwaker Gupta: > > 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? > hello Diwaker! you can always call a function that is defined extern that uses fprintf et. al. i doubt it's the prettiest way but at least it works. cheers m.