qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH 4/4] gdbstub: x86: Switch 64/32 bit registers dynamically
Date: Mon, 29 Jun 2009 16:22:11 +0200	[thread overview]
Message-ID: <4A48CE13.6050800@siemens.com> (raw)
In-Reply-To: <200906291507.05278.paul@codesourcery.com>

Paul Brook wrote:
>>>> No question, this is a gdb issue. But, as it was confirmed in several
>>>> discusssions with gdb people, it is a non-trivial thing to fix. So until
>>>> qemu finds a gdb version attach with a rework x86 support, we have to
>>>> work around it by switching the register layout as the guest switches
>>>> its execution mode between 16/32 and 64 bit.
>>> I still object to this patch. Especially as there's no indication that
>>> it's a harroble hack to workaround broken GDB.
>> Sorry, last sentence doesn't parse for me.
> 
> 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. You can only debug 32/16 bit
code with qemu (for i386) and 64 bit code with qemu-system-x86_64. But
those scenarios are not affected by my patch in any way.

> 
>> So what do you suggest for fixing this bug? 
> 
> Fix gdb.

It's not a one-liner, far more complex than this intermediate workaround.

> 
>> Do you have a patch at hand to fix gdb before 7.0?
> 
> No. I'm unconvinced by any argument that requires a specific GDB version. 
> You've known about this bug for a long time now.
> 

Please don't forget that it wasn't me to remove the workaround from qemu
before fixing gdb first. That workaround used to be there for a reason.

>> And a solution for older gdbs?
> 
> If you really care about old gdb, then you get to backport the changes.

To all standard distros out there in the field... (this is not just
about fixing my personal debug environment)

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux

  reply	other threads:[~2009-06-29 14:22 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 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 [this message]
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
2009-06-29 14:51           ` Paul Brook
2009-06-27  7:53 ` [Qemu-devel] [PATCH 1/4] gdbstub: Add vCont support 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 3/4] gdbstub: x86: Support for setting segment registers 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=4A48CE13.6050800@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=aliguori@us.ibm.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).