From: Jan Kiszka <jan.kiszka@web.de>
To: chimeranet89@gmail.com
Cc: qemu-devel <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:55:41 +0200 [thread overview]
Message-ID: <4C18837D.1050409@web.de> (raw)
In-Reply-To: <00163649a20d7ed8cb048920f1e0@google.com>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
[Please keep the list in CC]
chimeranet89@gmail.com wrote:
> I never thought about this, since I always used qemu + gdb without
> having this kind of trouble.. I just finished compiling version 0.12.4,
> and I will surely try what you are suggesting, I really appreciate your
> help.
The restriction doesn't bite you that hard when in flat mode, the mode
modern OSes run in most of the time. And you can manually work around it
to some degree by letting qemu dump the registers ("monitor info
registers") and doing some manual calculation, e.g. for offset-based
gs/fs addressing (per-CPU variable under Linux).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next parent reply other threads:[~2010-06-16 7:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00163649a20d7ed8cb048920f1e0@google.com>
2010-06-16 7:55 ` Jan Kiszka [this message]
2010-06-16 8:04 ` [Qemu-devel] Re: Re: [Bug 581353] Re: qemu doesn't stop execution upon hitting a breakpoint chimeranet89
[not found] <20100516152304.10489.35592.malonedeb@potassium.ubuntu.com>
2010-06-16 7:07 ` [Qemu-devel] " Alfredo Mungo
2010-06-16 7:20 ` Jun Koi
2010-06-16 7:40 ` [Qemu-devel] " Jan Kiszka
2010-06-16 7:43 ` 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
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=4C18837D.1050409@web.de \
--to=jan.kiszka@web.de \
--cc=chimeranet89@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).