From: Jan Kiszka <jan.kiszka@web.de>
To: Jun Koi <junkoi2004@gmail.com>
Cc: chimeranet89@gmail.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Bug 581353] Re: qemu doesn't stop execution upon hitting a breakpoint
Date: Wed, 16 Jun 2010 09:40:07 +0200 [thread overview]
Message-ID: <4C187FD7.5080601@web.de> (raw)
In-Reply-To: <AANLkTimKx6FTzaOXSk33TMqE358HIUwQrCJ8eR08zenc@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
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.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-06-16 7:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100516152304.10489.35592.malonedeb@potassium.ubuntu.com>
2010-06-16 7:07 ` [Qemu-devel] [Bug 581353] Re: qemu doesn't stop execution upon hitting a breakpoint Alfredo Mungo
2010-06-16 7:20 ` Jun Koi
2010-06-16 7:40 ` Jan Kiszka [this message]
2010-06-16 7:43 ` [Qemu-devel] " Jun Koi
2010-06-16 7:49 ` Jan Kiszka
2010-06-16 7:54 ` Jun Koi
2010-06-16 8:02 ` Jan Kiszka
2010-06-16 9:14 ` malc
2010-06-16 9:34 ` Jan Kiszka
2010-06-16 9:41 ` malc
2010-06-16 9:43 ` malc
2010-06-16 10:03 ` Gleb Natapov
2010-06-16 8:07 ` [Qemu-devel] " Alfredo Mungo
2016-08-17 9:56 ` T. Huth
[not found] <00163649a20d7ed8cb048920f1e0@google.com>
2010-06-16 7:55 ` [Qemu-devel] " Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C187FD7.5080601@web.de \
--to=jan.kiszka@web.de \
--cc=chimeranet89@gmail.com \
--cc=junkoi2004@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).