qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Debugging with paging enabled
Date: Wed, 8 Nov 2006 18:42:26 -0500	[thread overview]
Message-ID: <20061108234226.GA13464@nevyn.them.org> (raw)
In-Reply-To: <822249722.20061109003305@kilgus.net>

On Thu, Nov 09, 2006 at 12:33:05AM +0100, Marcel Kilgus wrote:
> Leaving that aside, if I do set the breakpoint correctly at virtual
> address (e.g.) 0xC0123456 qemu will (correctly I guess) cause an
> exception for code offset 0x123456 (as CS base is 0xC0000000). GDB
> however then doesn't recognize its own breakpoint as it only remembers
> having set one at 0xC0123456, and apparently doesn't translate the
> given exception address of CS:0x123456 back to a virtual one.

Which segment is it running from at this point?  Qemu may be reporting
the wrong address.

> So all in all GDB just doesn't seem to cope very well with segmented
> memory.

Correct.  It doesn't know anything at all about i386 segmentation.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-11-08 23:42 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 [this message]
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
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=20061108234226.GA13464@nevyn.them.org \
    --to=drow@false.org \
    --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).