From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hyqri-0008Ds-Pb for qemu-devel@nongnu.org; Thu, 14 Jun 2007 11:04:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hyqrh-0008BW-Hx for qemu-devel@nongnu.org; Thu, 14 Jun 2007 11:04:02 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hyqrh-0008BC-97 for qemu-devel@nongnu.org; Thu, 14 Jun 2007 11:04:01 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Hyqrg-0005hY-Fz for qemu-devel@nongnu.org; Thu, 14 Jun 2007 11:04:00 -0400 From: Paul Brook Subject: Re: [Qemu-devel] Debugging guest OS / tracing instruction pointer Date: Thu, 14 Jun 2007 16:03:52 +0100 References: <20070606095708.28535gmx1@mx017.gmx.net> <467152A6.9060805@gmx.at> In-Reply-To: <467152A6.9060805@gmx.at> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706141603.52939.paul@codesourcery.com> 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 Cc: Clemens Kolbitsch On Thursday 14 June 2007, Clemens Kolbitsch wrote: > hi! > i'm looking for a way to monitor the eip register. is there a simple way > to do this? i know that that produces tons of data... > > even better would be to know where i could intercept the main-loop > (exec_cpu ??) to check for a certain eip value... qemu already has mechanisms for supporting debugger breakpoints. Sounds like you want something very similar. Paul