From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Kxjcb-00019B-FL for qemu-devel@nongnu.org; Wed, 05 Nov 2008 09:44:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Kxjca-00018Y-Dv for qemu-devel@nongnu.org; Wed, 05 Nov 2008 09:44:36 -0500 Received: from [199.232.76.173] (port=51676 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Kxjca-00018Q-49 for qemu-devel@nongnu.org; Wed, 05 Nov 2008 09:44:36 -0500 Received: from lizzard.sbs.de ([194.138.37.39]:23331) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KxjcZ-0003Cb-MD for qemu-devel@nongnu.org; Wed, 05 Nov 2008 09:44:36 -0500 Message-ID: <4911B14B.2000803@siemens.com> Date: Wed, 05 Nov 2008 15:44:27 +0100 From: Jan Kiszka MIME-Version: 1.0 References: <491084F7.2050800@siemens.com> <200811041742.58859.paul@codesourcery.com> <49108D03.4000204@siemens.com> <20081105124309.GF13630@shareable.org> In-Reply-To: <20081105124309.GF13630@shareable.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] gdbstub: x86-64: reintroduce dynamic register sets 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: Paul Brook Jamie Lokier wrote: > Jan Kiszka wrote: >> Paul Brook wrote: >>> On Tuesday 04 November 2008, Jan Kiszka wrote: >>>> Commit 5459 broke the dynamic register set switching of qemu's gdbstub >>>> for x86-64. This prevents setting the correct architecture in gdb when >>>> debugging 32 or 16-bit code in a 64-bit emulator. Fix this. >>> Is this really a feature? Surely any attached gdb is going to break horribly >>> when we transition from a 64-bit to a 32-bit code segment. >> Well, it would be real feature if gdb was smart enough to track those >> switches automatically... >> >> However, you can (and obviously have to) call "set arch ..." after that >> switch in order to get the proper disassembly. Or you happen to use >> qemu-system-x86_64 with a 32-bit guest and fire up gdb with the >> appropriate 32-bit binary directly. Both used to work fine. > > How does it handle mixed 32-bit and 16-bit code? (Since you mentioned > it supports 16-bit code). > > Does that require manual intervention too? Same here: 'set arch i8086' will make gdb switch to 16-bit disassembly mode. But the remote protocol's register set format does not change then, compared to arch i386. BTW, more glue (including gdb patches) is required for full support of x86 segmentation. I'm currently trying to get out changes in shape again that were once based on older versions of qemu and gdb. Jan -- Siemens AG, Corporate Technology, CT SE 2 ES-OS Corporate Competence Center Embedded Linux