From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Cc: Andreas Schultz <aschultz@warp10.net>,
Paul Brook <paul@codesourcery.com>,
kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: gdbstub: packet reply is too long
Date: Tue, 30 Dec 2008 17:43:02 -0500 [thread overview]
Message-ID: <20081230224302.GA30049@caradoc.them.org> (raw)
In-Reply-To: <4958E5A7.4000303@web.de>
On Mon, Dec 29, 2008 at 03:58:47PM +0100, Jan Kiszka wrote:
> Well, in the current gdb design, current_gdbarch is consulted when
> disassembling the code while target_gdbarch defines the register set
> that is exchanged with the remote stub.
This is a transitional state. Really, there isn't supposed to be a
'current' gdbarch; we're already moving away from it.
Thinking about it some more you may be right about the overall
solution though, sorry. The target_gdbarch idea is likely to stick
around for a while. But some work will have to be done if current and
target architectures have different register sets :-(
> I'm pretty sure that the final solution will involve extended x86
> register sets in order to inform the frontend about the full target CPU
> state so that it can set the right current_gdbarch automatically.
Isn't everything we need for this in eflags already?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-12-30 22:43 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 12:42 gdbstub: packet reply is too long Andreas Schultz
2008-12-20 15:49 ` Jan Kiszka
2008-12-20 15:49 ` [Qemu-devel] " Jan Kiszka
2008-12-20 20:35 ` Paul Brook
2008-12-20 20:35 ` Paul Brook
2008-12-20 21:00 ` Jan Kiszka
2008-12-20 21:00 ` Jan Kiszka
2008-12-20 21:03 ` Paul Brook
2008-12-20 21:03 ` Paul Brook
2008-12-20 21:22 ` Jan Kiszka
2008-12-20 21:22 ` Jan Kiszka
2008-12-20 21:34 ` Paul Brook
2008-12-20 21:34 ` Paul Brook
2008-12-20 21:55 ` Jan Kiszka
2008-12-20 21:55 ` Jan Kiszka
2008-12-20 22:08 ` Paul Brook
2008-12-20 22:08 ` Paul Brook
2008-12-20 22:34 ` Jan Kiszka
2008-12-20 22:34 ` Jan Kiszka
2008-12-20 22:46 ` Paul Brook
2008-12-20 22:46 ` Paul Brook
2008-12-20 23:44 ` Jan Kiszka
2008-12-20 23:44 ` Jan Kiszka
2008-12-26 23:30 ` Daniel Jacobowitz
2008-12-26 23:30 ` [Qemu-devel] " Daniel Jacobowitz
2008-12-29 14:58 ` Jan Kiszka
2008-12-29 14:58 ` [Qemu-devel] " Jan Kiszka
2008-12-30 22:43 ` Daniel Jacobowitz [this message]
2009-01-02 12:53 ` Jan Kiszka
2009-01-02 12:53 ` Jan Kiszka
2009-01-03 1:53 ` Jamie Lokier
2009-01-03 1:53 ` Jamie Lokier
2009-01-04 13:50 ` Jan Kiszka
2009-01-04 13:50 ` 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=20081230224302.GA30049@caradoc.them.org \
--to=drow@false.org \
--cc=aschultz@warp10.net \
--cc=kvm@vger.kernel.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.