From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Brook Subject: Re: [Qemu-devel] Re: gdbstub: packet reply is too long Date: Sat, 20 Dec 2008 21:34:00 +0000 Message-ID: <200812202134.01169.paul@codesourcery.com> References: <1229776952.22890.2.camel@ws-aschultz> <200812202103.19216.paul@codesourcery.com> <494D620A.8020102@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Andreas Schultz , kvm@vger.kernel.org To: qemu-devel@nongnu.org Return-path: Received: from mail.codesourcery.com ([65.74.133.4]:46080 "EHLO mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753715AbYLTVeF (ORCPT ); Sat, 20 Dec 2008 16:34:05 -0500 In-Reply-To: <494D620A.8020102@web.de> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: > >> 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? Because, as I've said several times before, the "automatic switching" is wrong. It may happen to work in your very limited circumstances, but there are many fairly common circumstances (e.g. stepping between a 64-bit kernel and a 32-bit userspace) where it's just plain broken. I object strongly to a "fix" that prevents a proper gdb from working. > 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 Really? I'm pretty sure other architectures already manage it. Paul