From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 4/4] gdbstub: x86: Switch 64/32 bit registers dynamically
Date: Tue, 30 Jun 2009 14:00:36 +0200 [thread overview]
Message-ID: <4A49FE64.2000109@siemens.com> (raw)
In-Reply-To: <4A49BB74.4080504@redhat.com>
Gerd Hoffmann wrote:
> On 06/29/09 16:43, Paul Brook wrote:
>>>> You've just deliberately broken the qemu gdbstub. After your patch
>>>> it is
>>>> impossible to debug mixed 32/64-bit code.
>>> Please give it a try as it's the other way around: You can't properly
>>> debug mixed target code without my patch.
>>
>> Sure you can, you just need a gdb that doesn't suck. As soon as you
>> encounter
>> actual mixed code (rather than just running the wrong qemu) your patch
>> causes
>> things to die horribly.
>
> i.e. the latest gdb release (6.8) works better *with* the workaround,
> and the latest gdb bits from cvs work better *without* the workaround.
> Is that correct?
Nope, even today's gdb requires my patch to work properly in these mixed
scenarios.
>
> How about making it runtime-switchable then, so qemu can deal with both
> cases?
I hope we will once be able to automatically detected improved gdb
versions. For now I see no need for a command line or whatever switch.
But I'm always open to learn about steps that work without it and fail
when it's applied. I'm not aware of any.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-06-30 12:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 7:53 [Qemu-devel] [RESEND][PATCH 0/4] Long pending gdbstub patches Jan Kiszka
2009-06-27 7:53 ` [Qemu-devel] [PATCH 3/4] gdbstub: x86: Support for setting segment registers Jan Kiszka
2009-06-27 7:53 ` [Qemu-devel] [PATCH 2/4] gdbstub: x86: Refactor register access Jan Kiszka
2009-06-27 7:53 ` [Qemu-devel] [PATCH 1/4] gdbstub: Add vCont support Jan Kiszka
2009-06-27 7:53 ` [Qemu-devel] [PATCH 4/4] gdbstub: x86: Switch 64/32 bit registers dynamically Jan Kiszka
2009-06-29 13:01 ` [Qemu-devel] " Paul Brook
2009-06-29 13:42 ` Jan Kiszka
2009-06-29 14:07 ` Paul Brook
2009-06-29 14:22 ` Jan Kiszka
2009-06-29 14:43 ` Paul Brook
2009-06-29 14:53 ` Jan Kiszka
2009-06-29 15:16 ` Daniel Jacobowitz
2009-06-29 15:36 ` Jan Kiszka
2009-06-29 22:00 ` Jamie Lokier
2009-06-30 11:54 ` Jan Kiszka
2009-06-30 7:15 ` Gerd Hoffmann
2009-06-30 12:00 ` Jan Kiszka [this message]
2009-06-29 14:51 ` Paul Brook
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=4A49FE64.2000109@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@us.ibm.com \
--cc=kraxel@redhat.com \
--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 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).