From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Cc: Marcel Kilgus <qemu@mail.kilgus.net>
Subject: Re: [Qemu-devel] Re: Debugging with paging enabled
Date: Fri, 10 Nov 2006 12:10:32 -0500 [thread overview]
Message-ID: <20061110171032.GA29431@nevyn.them.org> (raw)
In-Reply-To: <200611101556.02645.paul@codesourcery.com>
On Fri, Nov 10, 2006 at 03:56:01PM +0000, Paul Brook wrote:
> > Assuming that breakpoint locations are indeed meant to be virtual
> > addresses, GDB would have to evaluate the CS descriptor, add the CS
> > base to the EIP address and THEN check whether it knows the address.
> > But as it seems to be segment-agnostic it doesn't do that and things
> > break as a result.
>
> As Dan said, gdb knows nothing about x86 segmentation. As soon as you have
> nonzero segment bases you're pretty much on your own.
>
> If you care about fixing this I suggest you get GDB folks to agree (and
> document) how segmented memory models should work, then implement that model
> in qemu. Hacking qemu to work for your particular case with unmodified gdb
> probably "breaks" something else, so doesn't seem to improve the overall
> usefulness.
I'd recommend the even simpler hack of having qemu report a PC that
included the segment base :-)
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-11-10 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 2:30 [Qemu-devel] Debugging with paging enabled Marcel Kilgus
2006-11-08 21:13 ` [Qemu-devel] " Marcel Kilgus
2006-11-08 22:15 ` Fabrice Bellard
2006-11-08 23:33 ` Marcel Kilgus
2006-11-08 23:42 ` Daniel Jacobowitz
2006-11-08 23:57 ` Marcel Kilgus
2006-11-09 2:24 ` Daniel Jacobowitz
2006-11-10 13:14 ` andrzej zaborowski
2006-11-10 14:31 ` Marcel Kilgus
2006-11-10 15:56 ` Paul Brook
2006-11-10 16:14 ` Marcel Kilgus
2006-11-10 17:10 ` Daniel Jacobowitz [this message]
2006-11-10 19:01 ` Marcel Kilgus
2006-11-10 19:07 ` Daniel Jacobowitz
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=20061110171032.GA29431@nevyn.them.org \
--to=drow@false.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu@mail.kilgus.net \
/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).