From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=56003 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OOnHP-0005wU-Ng
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:43:24 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <junkoi2004@gmail.com>) id 1OOnHO-000555-KD
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:43:23 -0400
Received: from mail-pw0-f45.google.com ([209.85.160.45]:48640)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <junkoi2004@gmail.com>) id 1OOnHO-00054x-Fm
	for qemu-devel@nongnu.org; Wed, 16 Jun 2010 03:43:22 -0400
Received: by pwj7 with SMTP id 7so346622pwj.4
	for <qemu-devel@nongnu.org>; Wed, 16 Jun 2010 00:43:21 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <4C187FD7.5080601@web.de>
References: <20100516152304.10489.35592.malonedeb@potassium.ubuntu.com>
	<20100616070748.20899.45040.malone@wampee.canonical.com>
	<AANLkTimKx6FTzaOXSk33TMqE358HIUwQrCJ8eR08zenc@mail.gmail.com>
	<4C187FD7.5080601@web.de>
From: Jun Koi <junkoi2004@gmail.com>
Date: Wed, 16 Jun 2010 16:43:01 +0900
Message-ID: <AANLkTininnM-xOUW00PQwGXidAAs-8YXe3F5mu9pvLUP@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Subject: [Qemu-devel] Re: [Bug 581353] Re: qemu doesn't stop execution upon
	hitting a breakpoint
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.nongnu.org/archive/html/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: Jan Kiszka <jan.kiszka@web.de>
Cc: chimeranet89@gmail.com, qemu-devel@nongnu.org

On Wed, Jun 16, 2010 at 4:40 PM, Jan Kiszka <jan.kiszka@web.de> wrote:
> Jun Koi wrote:
>> On Wed, Jun 16, 2010 at 4:07 PM, Alfredo Mungo <chimeranet89@gmail.com> wrote:
>>> Same thing happens to me, same versions as above.. I must turn to
>>> another app to accomplish my work while awaiting for a bug-fix, the code
>>> is perfectly executed but while gdb hits the breakpoints qemu goes on..
>>>
>>> --
>>> qemu doesn't stop execution upon hitting a breakpoint
>>> https://bugs.launchpad.net/bugs/581353
>>> You received this bug notification because you are a member of qemu-
>>> devel-ml, which is subscribed to QEMU.
>>
>> i think this bug has been fixed in 0.12.4. have you tried that??
>
> Or this is a well-known gdb deficit: if the bootloader operates in
> real-mode, you have to set two breakpoints, one at the linear address to
> make qemu catch it, and another one at the segment offset to avoid gdb
> skipping the exit due to ip != bp-addr.
>
> gdb is still fairly restricted when it comes to system-level debugging,
> specifically as it lacks support for special x86 registers and the
> segmented addressing mode.

what do you mean by "it lacks support for special x86 registers" ?

thanks,
J