From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KlPWc-0007bQ-GQ for qemu-devel@nongnu.org; Thu, 02 Oct 2008 10:51:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KlPWa-0007XW-5v for qemu-devel@nongnu.org; Thu, 02 Oct 2008 10:51:29 -0400 Received: from [199.232.76.173] (port=48821 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KlPWZ-0007XH-OQ for qemu-devel@nongnu.org; Thu, 02 Oct 2008 10:51:27 -0400 Received: from ti-out-0910.google.com ([209.85.142.191]:43895) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KlPWX-0005KV-E6 for qemu-devel@nongnu.org; Thu, 02 Oct 2008 10:51:26 -0400 Received: by ti-out-0910.google.com with SMTP id y6so509615tia.18 for ; Thu, 02 Oct 2008 07:51:21 -0700 (PDT) Message-ID: Date: Thu, 2 Oct 2008 21:51:21 +0700 From: "Mulyadi Santosa" Subject: Re: [Qemu-devel] Documentation/tools on debuging dyngen code? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081001184025.GA70684@saturn.kn-bremen.de> <20081001202009.GA21305@networkno.de> 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 On 10/2/08, Bruce Beare (bbeare) wrote: > I'm working on a 2.6.24 Linux port built for ARCH=powerpc and configured > for the PReP machine. I have the port booting using an unmodified 0.9.1 > version (actually, head from the SVN repo) of qemu-system-ppc but > sometimes find that QEMU "hangs". Analysis of the hang reveals: > > o C-A C-X does not respond > o QEMU is sucking up 100% cpu time of one processor > o GDB to the kernel debug port (qemu option -s -p 1234) is non > responsive > o ltrace, strace show no system or library calls in progress > o GDB on QEMU shows that it is executing apparently valid code in the > 0x4xxxxxxx > range. > > My conclusion is that QEMU is looping while executing the dynamically > generated code. I'd like to debug this further... and am looking for > some pointers on how to do so. Is there a built-in debugger? Is there a > particular probe point that I should set a GDB breakpoint on? What is > the general procedure for doing this level of debug? I suggest to observe the generated code first. Explore the -d option of qemu. For complete list of what you can log, use "qemu -d ?". regards, Mulyadi