From: Jan Kiszka <jan.kiszka@web.de>
To: Andreas Schultz <aschultz@warp10.net>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: gdbstub: packet reply is too long
Date: Sat, 20 Dec 2008 16:49:08 +0100 [thread overview]
Message-ID: <494D13F4.2040609@web.de> (raw)
In-Reply-To: <1229776952.22890.2.camel@ws-aschultz>
[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]
Andreas Schultz wrote:
> Hi,
>
> I'm trying to debug a 32bit (i386) kernel on a 64bit host under kvm, but
> gdb always refuses it with:
> Remote 'g' packet reply is too long:
> 0000000000000000000000000000000000000000000000002306000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000f0ff0000000000000230020000f00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007f0300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
> 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
>
> I tried kvm-79 and kvm-git from today. gdb is v6.8 (ubuntu intrepid)
>
> Any hints?
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).
In the meantime, you may want to have a look at my kvm [1] or qemu patch
queue [2]. Note that unless you provide a binary to gdb that is 32 bit
already, you may have to switch the architecture manually ("set arch
i386" or "i8086") before attaching.
Jan
[1] git://git.kiszka.org/kvm-userspace.git gdb-queue
[2] git://git.kiszka.org/qemu.git gdb-queue
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 258 bytes --]
next parent reply other threads:[~2008-12-20 15:49 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 ` Jan Kiszka [this message]
2008-12-20 20:35 ` [Qemu-devel] Re: gdbstub: packet reply is too long Paul Brook
2008-12-20 21:00 ` Jan Kiszka
2008-12-20 21:03 ` Paul Brook
2008-12-20 21:22 ` Jan Kiszka
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=494D13F4.2040609@web.de \
--to=jan.kiszka@web.de \
--cc=aschultz@warp10.net \
--cc=kvm@vger.kernel.org \
--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).