From: Paul Brook <paul@codesourcery.com>
To: Jan Kiszka <jan.kiszka@siemens.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 15:43:33 +0100 [thread overview]
Message-ID: <200906291543.34071.paul@codesourcery.com> (raw)
In-Reply-To: <4A48CE13.6050800@siemens.com>
> > 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.
Paul
next prev parent reply other threads:[~2009-06-29 14:43 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 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 [this message]
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
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=200906291543.34071.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.com \
--cc=jan.kiszka@siemens.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).