qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Richard Henderson <rth@twiddle.net>
Cc: Doug Evans <dje@google.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] x86: Fix x86_64 'g' packet response to gdb from 32-bit mode.
Date: Fri, 4 Nov 2016 16:34:28 +0000	[thread overview]
Message-ID: <CAFEAcA8q-+r-XZ7H39ma7+ZhhO8L2haVzxqosGDvxaY2_tFAQA@mail.gmail.com> (raw)
In-Reply-To: <a69e7832-55a5-9e2b-1b95-17ecd30fd96b@twiddle.net>

On 4 November 2016 at 16:29, Richard Henderson <rth@twiddle.net> wrote:
> On 11/03/2016 05:35 PM, Doug Evans wrote:
>>
>> The remote protocol can't handle flipping back and forth
>> between 32-bit and 64-bit regs. To compensate, pretend "as if"
>> on 64-bit cpu when in 32-bit mode.
>>
>> Signed-off-by: Doug Evans <dje@google.com>
>> ---
>>  target-i386/gdbstub.c | 52
>> ++++++++++++++++++++++++++++++++++++++-------------
>>  1 file changed, 39 insertions(+), 13 deletions(-)
>
>
> Reviewed-by: Richard Henderson <rth@twiddle.net>

Has anybody ever looked at fixing this on the gdb end?
(There are some similar cases for ARM CPUs, and actually
being able to debug across 32/64 boundaries, big/little
endian boundaries etc would be quite handy in some
situations.)

thanks
-- PMM

  reply	other threads:[~2016-11-04 16:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-03 23:35 [Qemu-devel] [PATCH] x86: Fix x86_64 'g' packet response to gdb from 32-bit mode Doug Evans
2016-11-04 16:29 ` Richard Henderson
2016-11-04 16:34   ` Peter Maydell [this message]
2016-11-04 19:01     ` Pedro Alves
2016-11-04 19:27       ` Doug Evans
2016-12-14 17:14 ` Paolo Bonzini
2016-12-14 17:39   ` Doug Evans

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=CAFEAcA8q-+r-XZ7H39ma7+ZhhO8L2haVzxqosGDvxaY2_tFAQA@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=dje@google.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.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).