From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LGM8K-00040l-Jh for qemu-devel@nongnu.org; Fri, 26 Dec 2008 18:30:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LGM8I-0003ym-6e for qemu-devel@nongnu.org; Fri, 26 Dec 2008 18:30:19 -0500 Received: from [199.232.76.173] (port=45835 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LGM8I-0003yc-0M for qemu-devel@nongnu.org; Fri, 26 Dec 2008 18:30:18 -0500 Received: from nan.false.org ([208.75.86.248]:55461) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LGM8H-0002l3-Ni for qemu-devel@nongnu.org; Fri, 26 Dec 2008 18:30:17 -0500 Date: Fri, 26 Dec 2008 18:30:12 -0500 From: Daniel Jacobowitz Subject: Re: [Qemu-devel] Re: gdbstub: packet reply is too long Message-ID: <20081226233012.GA9221@caradoc.them.org> References: <1229776952.22890.2.camel@ws-aschultz> <200812202208.34044.paul@codesourcery.com> <494D72E1.6020104@web.de> <200812202246.39036.paul@codesourcery.com> <494D8344.8010203@web.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <494D8344.8010203@web.de> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Andreas Schultz , Paul Brook , kvm@vger.kernel.org On Sun, Dec 21, 2008 at 12:44:04AM +0100, Jan Kiszka wrote: > And that means setting current_gdbarch while keeping target_gdbarch - > that's where reality (existing gdb code) bites us. Again, I'm not > arguing against fixing this, I'm arguing in keeping qemu's workaround > until this is done. I will look into the gdb part, but one after the other. No, it does not mean setting current_gdbarch different from target_gdbarch. With the current gdbarch set to a 64-bit one that accurately describes the target, GDB should be able to debug code running in 32-bit mode. If it can't, there are simply bugs in GDB to fix. If you'd like to reach some solution to this problem, which I've seen come up on the QEMU list a half-dozen times now, please describe how you're using GDB on the gdb@sourceware.org mailing list and let's see if we can't fix the GDB bugs. I'm pretty sure that any solution is going to involve always transferring the x86-64 register set, though. -- Daniel Jacobowitz CodeSourcery