From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1EpJAM-0002F4-KV
	for qemu-devel@nongnu.org; Thu, 22 Dec 2005 00:39:02 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1EpJAK-0002Be-AQ
	for qemu-devel@nongnu.org; Thu, 22 Dec 2005 00:39:02 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1EpJAK-0002BT-74
	for qemu-devel@nongnu.org; Thu, 22 Dec 2005 00:39:00 -0500
Received: from [66.54.152.27] (helo=jive.SoftHome.net)
	by monty-python.gnu.org with smtp (Exim 4.34) id 1EpJ9O-0008NL-8G
	for qemu-devel@nongnu.org; Thu, 22 Dec 2005 00:38:02 -0500
From: Mulyadi Santosa <a_mulyadi@softhome.net>
Subject: Re: [Qemu-devel] Problems with gdbserver and debugging
Date: Thu, 22 Dec 2005 12:31:40 +0700
References: <16af12af0512211843h2c73e20v72ec61d150eb13d7@mail.gmail.com>
In-Reply-To: <16af12af0512211843h2c73e20v72ec61d150eb13d7@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200512221231.40710.a_mulyadi@softhome.net>
Reply-To: a_mulyadi@softhome.net, 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, Andre Pech <apech@arastra.com>

Hello Andre...

> I'm running into problems using qemu to debug a kernel module. My
> host and virtual machine are both x86 running Fedora Core 4. After
> insmoding the module in the virtual machine, starting gdbserver,
> running gdb on the host with the module sections loaded at the right
> place, and setting a breakpoint in the module code, gdb does not
> always get notified when the code is exectuted. After adding

I'm not doing module debugging, only core kernel code debugging, but 
more or less I run into same situation (last time confirmed with Qemu 
0.7.1)

For additional info, sometimes I also suffered the other condition. 
Breakpoint is hit, but even if I delete it, the emulation still stops 
whenever the code at related physical address is hit. I tried to 
printf() every gdb command received by Qemu's gdbstub and it confirmed 
that breakpoint deletion command is actually received, but I can't 
confirm what is the real bug there.

regards

Mulyadi