From: Marcel Kilgus <qemu@mail.kilgus.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Debugging with paging enabled
Date: Fri, 10 Nov 2006 17:14:19 +0100 [thread overview]
Message-ID: <1978675291.20061110171419@kilgus.net> (raw)
In-Reply-To: <200611101556.02645.paul@codesourcery.com>
Paul Brook wrote:
> As Dan said, gdb knows nothing about x86 segmentation. As soon as you have
> nonzero segment bases you're pretty much on your own.
I was just wondering, because I didn't invent that "move the code to
3GB base" but it is (was?) the model used by Linux, at least in very
early versions (I'm not accustomed with the current code base). So I
didn't expect to be the first person stumbling over this shortcoming.
> 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.
Nah, I've already spent way more time on this than I can really
afford, though it was quite fun for a change. And my hack works
perfectly for my needs, so I'm fine. At least my findings are now
documented in the list archives and anybody with a similar problem can
now read it up.
All the best, Marcel
next prev parent reply other threads:[~2006-11-10 16:14 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 [this message]
2006-11-10 17:10 ` Daniel Jacobowitz
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=1978675291.20061110171419@kilgus.net \
--to=qemu@mail.kilgus.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.