From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MLIaq-0002CN-E9 for qemu-devel@nongnu.org; Mon, 29 Jun 2009 11:16:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MLIal-0002Ax-Oj for qemu-devel@nongnu.org; Mon, 29 Jun 2009 11:16:28 -0400 Received: from [199.232.76.173] (port=37816 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MLIal-0002Ap-20 for qemu-devel@nongnu.org; Mon, 29 Jun 2009 11:16:23 -0400 Received: from mx20.gnu.org ([199.232.41.8]:36640) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MLIak-0003ED-1O for qemu-devel@nongnu.org; Mon, 29 Jun 2009 11:16:22 -0400 Received: from nan.false.org ([208.75.86.248]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MLIae-0003Uc-A0 for qemu-devel@nongnu.org; Mon, 29 Jun 2009 11:16:16 -0400 Date: Mon, 29 Jun 2009 11:16:13 -0400 From: Daniel Jacobowitz Subject: Re: [Qemu-devel] Re: [PATCH 4/4] gdbstub: x86: Switch 64/32 bit registers dynamically Message-ID: <20090629151613.GA5924@caradoc.them.org> References: <20090627075350.13376.17936.stgit@mchn012c.ww002.siemens.net> <200906291507.05278.paul@codesourcery.com> <4A48CE13.6050800@siemens.com> <200906291543.34071.paul@codesourcery.com> <4A48D579.8000305@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A48D579.8000305@siemens.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Anthony Liguori , Paul Brook , qemu-devel@nongnu.org On Mon, Jun 29, 2009 at 04:53:45PM +0200, Jan Kiszka wrote: > Just to recall the situation (again, please actually try it): if you > have to debug code that switches between 16/32 bit and 64 bit, you > _can't_ debug the 16 or 32 bit part as gdb will stumble and fall over > qemu sending 64-bit register layout for 16/32 bit code. That is a gdb > limitation, but this patch is about dealing with it until it's resolved > in gdb. Remind me why you can't just tell GDB that the target is 64-bit despite whatever file you've given it? -- Daniel Jacobowitz CodeSourcery