From: Jan Kiszka <jan.kiszka@web.de>
To: Paul Brook <paul@codesourcery.com>
Cc: Andreas Schultz <aschultz@warp10.net>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: gdbstub: packet reply is too long
Date: Sat, 20 Dec 2008 22:22:18 +0100 [thread overview]
Message-ID: <494D620A.8020102@web.de> (raw)
In-Reply-To: <200812202103.19216.paul@codesourcery.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
Paul Brook wrote:
> On Saturday 20 December 2008, Jan Kiszka wrote:
>> Paul Brook wrote:
>>>>> I'm trying to debug a 32bit (i386) kernel on a 64bit host under kvm,
>>>>> but gdb always refuses it with:
>>>> QEMU and also KVM's x86_64 version are currently broken /wrt debugging
>>>> targets < 64 bits. I've posted a fix a while ago, but there were
>>>> concerns that gdb should better be enhanced (which is basically true,
>>>> but unrealistic to achieve in the near future).
>>> I still maintain that making the g packet format depend on the current
>>> CPU more is absolutely the wrong way to fix this.
>> From a higher perspective, it is surely not the cleanest approach. But
>> it still appears to be the only one which helps us working around this
>> gdb shortcoming.
>
> Actually it isn't. You could add an explicit switch.
And what would this buy us? I would have to go from your gdb terminal to
qemu, probably the monitor, just to switch manually what now happens
automatically. I don't see the case where you wouldn't want to switch
when you try to debug 16 or 32 bit code, so what would be the gain? Or
do you want some switch to disable this automatic register format switching?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2008-12-20 21:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1229776952.22890.2.camel@ws-aschultz>
2008-12-20 15:49 ` [Qemu-devel] Re: gdbstub: packet reply is too long Jan Kiszka
2008-12-20 20:35 ` Paul Brook
2008-12-20 21:00 ` Jan Kiszka
2008-12-20 21:03 ` Paul Brook
2008-12-20 21:22 ` Jan Kiszka [this message]
2008-12-20 21:34 ` Paul Brook
2008-12-20 21:55 ` Jan Kiszka
2008-12-20 22:08 ` Paul Brook
2008-12-20 22:34 ` Jan Kiszka
2008-12-20 22:46 ` Paul Brook
2008-12-20 23:44 ` Jan Kiszka
2008-12-26 23:30 ` Daniel Jacobowitz
2008-12-29 14:58 ` Jan Kiszka
2008-12-30 22:43 ` Daniel Jacobowitz
2009-01-02 12:53 ` Jan Kiszka
2009-01-03 1:53 ` Jamie Lokier
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=494D620A.8020102@web.de \
--to=jan.kiszka@web.de \
--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 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).