From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HvusK-0006ZQ-Sq for qemu-devel@nongnu.org; Wed, 06 Jun 2007 08:44:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HvusJ-0006Z1-9Q for qemu-devel@nongnu.org; Wed, 06 Jun 2007 08:44:32 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HvusI-0006Yy-Tr for qemu-devel@nongnu.org; Wed, 06 Jun 2007 08:44:31 -0400 Received: from nz-out-0506.google.com ([64.233.162.236]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HvusI-00063g-9B for qemu-devel@nongnu.org; Wed, 06 Jun 2007 08:44:30 -0400 Received: by nz-out-0506.google.com with SMTP id 18so249486nzp for ; Wed, 06 Jun 2007 05:44:29 -0700 (PDT) From: "xdutaotao" Date: Wed, 6 Jun 2007 20:43:52 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000E_01C7A87B.6B691100" Message-ID: <4666ac2b.09d5a4ca.4abf.ffffc928@mx.google.com> Subject: [Qemu-devel] How to debug QEMU with GDB?? 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 This is a multi-part message in MIME format. ------=_NextPart_000_000E_01C7A87B.6B691100 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I want to debug QEMU, but unfortunately after I set breakpoint in someplace of QEMU, then continue to run, GDB give me the message: "Continuing. Warning: Cannot insert breakpoint 1. Error accessing memory address 0x2dad0: IN/OUT ERROR." So I have to ask some question here? 1) How to find bug in QEMU if GDB doesn't work with QEMU? 2) What did you do when you must test your code of QEMU? Thank you! ------=_NextPart_000_000E_01C7A87B.6B691100 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

I want to debug QEMU, but unfortunately after I = set breakpoint in someplace of QEMU, then continue to run, GDB give me the = message:

“Continuing.

Warning:

Cannot insert breakpoint = 1.

Error accessing memory address 0x2dad0: IN/OUT = ERROR.”

So I have to ask some question = here?

1) = How to find bug in QEMU if GDB doesn't work with = QEMU?

2) = What did you do when you must test your code of = QEMU?

Thank you!

------=_NextPart_000_000E_01C7A87B.6B691100-- From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HwDbt-0007MP-0l for qemu-devel@nongnu.org; Thu, 07 Jun 2007 04:44:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HwDbr-0007M7-1p for qemu-devel@nongnu.org; Thu, 07 Jun 2007 04:44:48 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HwDbq-0007Lz-RI for qemu-devel@nongnu.org; Thu, 07 Jun 2007 04:44:46 -0400 Received: from jive.softhome.net ([66.54.152.27]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1HwDbp-00026S-Ar for qemu-devel@nongnu.org; Thu, 07 Jun 2007 04:44:45 -0400 Message-ID: <4667C7DA.4080309@softhome.net> Date: Thu, 07 Jun 2007 15:54:50 +0700 From: Mulyadi Santosa MIME-Version: 1.0 Subject: Re: [Qemu-devel] How to debug QEMU with GDB?? References: <4666ac2b.09d5a4ca.4abf.ffffc928@mx.google.com> In-Reply-To: <4666ac2b.09d5a4ca.4abf.ffffc928@mx.google.com> Content-Type: text/plain; charset=UTF-8; format=flowed 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 Cc: xdutaotao@gmail.com Hi... Probably, it doesn't help you much, but have you check Qemu user forum (http://qemu-forum.ipi.fi/)? There, in pending patch section, you can find a patch that makes Qemu more gdb-friendly. Another point is, are you sure you are putting breakpoint in .text segment? Also, it is possible that some memory address range is write protected (via mprotect) so you can't write there. Jasson Wessel is the man I know who works closely with qemu-gdb related stuffs... try to ask him. regards, Mulyadi