From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] gdbstub: x86-64: reintroduce dynamic register sets
Date: Wed, 5 Nov 2008 12:43:09 +0000 [thread overview]
Message-ID: <20081105124309.GF13630@shareable.org> (raw)
In-Reply-To: <49108D03.4000204@siemens.com>
Jan Kiszka wrote:
> Paul Brook wrote:
> > On Tuesday 04 November 2008, Jan Kiszka wrote:
> >> Commit 5459 broke the dynamic register set switching of qemu's gdbstub
> >> for x86-64. This prevents setting the correct architecture in gdb when
> >> debugging 32 or 16-bit code in a 64-bit emulator. Fix this.
> >
> > Is this really a feature? Surely any attached gdb is going to break horribly
> > when we transition from a 64-bit to a 32-bit code segment.
>
> Well, it would be real feature if gdb was smart enough to track those
> switches automatically...
>
> However, you can (and obviously have to) call "set arch ..." after that
> switch in order to get the proper disassembly. Or you happen to use
> qemu-system-x86_64 with a 32-bit guest and fire up gdb with the
> appropriate 32-bit binary directly. Both used to work fine.
How does it handle mixed 32-bit and 16-bit code? (Since you mentioned
it supports 16-bit code).
Does that require manual intervention too?
-- Jamie
next prev parent reply other threads:[~2008-11-05 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 17:23 [Qemu-devel] [PATCH] gdbstub: x86-64: reintroduce dynamic register sets Jan Kiszka
2008-11-04 17:42 ` Paul Brook
2008-11-04 17:57 ` Jan Kiszka
2008-11-05 12:43 ` Jamie Lokier [this message]
2008-11-05 14:44 ` [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=20081105124309.GF13630@shareable.org \
--to=jamie@shareable.org \
--cc=paul@codesourcery.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 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.