From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1FCik1-0005Fj-Vc
	for qemu-devel@nongnu.org; Fri, 24 Feb 2006 14:36:38 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1FCijz-0005Bs-QO
	for qemu-devel@nongnu.org; Fri, 24 Feb 2006 14:36:36 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1FCXed-0006qV-1q
	for qemu-devel@nongnu.org; Fri, 24 Feb 2006 02:46:22 -0500
Received: from [66.249.82.194] (helo=xproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1FCXeh-0005t8-NV
	for qemu-devel@nongnu.org; Fri, 24 Feb 2006 02:46:23 -0500
Received: by xproxy.gmail.com with SMTP id s10so185496wxc
	for <qemu-devel@nongnu.org>; Thu, 23 Feb 2006 23:46:17 -0800 (PST)
Message-ID: <1fa17f810602232346j26c301d3oeafe3220b9b0f1c3@mail.gmail.com>
Date: Fri, 24 Feb 2006 15:46:17 +0800
From: prime <guomingyan@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_22961_26015159.1140767177675"
Subject: [Qemu-devel] Make QEMU more friendly for kernel debug
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

------=_Part_22961_26015159.1140767177675
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello everyone,
   I find that I can't single step OS kernels use qemu.When I use "step" or
"next" command in gdb,
the kernel always enter its interrupt route instead
 of executing the next instruction after the breakpoint.So I modify QEMU's
source code to disable interrupts in single step mode,and now I can use
 "step" or "next" command in gdb to single step
 functions.

   Should I post the patch? It is a very small modification.


--
Three passions, simple but overwhelmingly strong, have governed my life:
the longing for love, the search for knowledge, and unbearable pity for
the suffering of mankind.
                         ---------Bertrand Russell

------=_Part_22961_26015159.1140767177675
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hello everyone,<br>

&nbsp;&nbsp; I find that I can't single step OS kernels use qemu.When I use=
 &quot;step&quot; or &quot;next&quot; command in gdb,<br>
the kernel always enter its interrupt route instead<br>
&nbsp;of executing the next instruction after the breakpoint.So I
modify QEMU's source code to disable interrupts in single step mode,and
now I can use<br>
&nbsp;&quot;step&quot; or &quot;next&quot; command in gdb to single step<br=
>
&nbsp;functions.<br>

<br>

&nbsp;&nbsp; Should I post the patch? It is a very small modification.<br c=
lear=3D"all">
<span><br></span><br>-- <br>Three passions, simple but overwhelmingly stron=
g, have governed my life: <br>the longing for love, the search for knowledg=
e, and unbearable pity for <br>the suffering of mankind.<br>&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
---------Bertrand Russell<br>

------=_Part_22961_26015159.1140767177675--