From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [Qemu-devel] Re: gdbstub: packet reply is too long Date: Sat, 20 Dec 2008 22:00:31 +0100 Message-ID: <494D5CEF.2040203@web.de> References: <1229776952.22890.2.camel@ws-aschultz> <494D13F4.2040609@web.de> <200812202035.33830.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig21AD2FEE53EED0C4FBE26EC7" Cc: qemu-devel@nongnu.org, Andreas Schultz , kvm@vger.kernel.org To: Paul Brook Return-path: Received: from fmmailgate02.web.de ([217.72.192.227]:44622 "EHLO fmmailgate02.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753181AbYLTVBg (ORCPT ); Sat, 20 Dec 2008 16:01:36 -0500 In-Reply-To: <200812202035.33830.paul@codesourcery.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig21AD2FEE53EED0C4FBE26EC7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Paul Brook wrote: >>> I'm trying to debug a 32bit (i386) kernel on a 64bit host under kvm, = but >>> gdb always refuses it with: >=20 >> 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). >=20 > I still maintain that making the g packet format depend on the current = CPU=20 > more is absolutely the wrong way to fix this. =46rom 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. There are internal issues in gdb (hard coupling of current and target arch) that will not allow this to be fixed in the near future, check the code (or my posting I sent out last month). Moreover, this only restores qemu to a state that it used to have for quite a while. I really wonder why we should voluntarily break this support for the users. Jan --------------enig21AD2FEE53EED0C4FBE26EC7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklNXPQACgkQniDOoMHTA+k5SQCfbJUaFPCREale6a1gxCA3fDgw 5kAAniQdy0bMtPA4GYhMFUGyf7YqIG82 =4r6p -----END PGP SIGNATURE----- --------------enig21AD2FEE53EED0C4FBE26EC7--