From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MPKQL-0006xx-SI for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:02:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MPKQH-0006qI-0F for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:02:17 -0400 Received: from [199.232.76.173] (port=59003 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MPKQG-0006po-MK for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:02:12 -0400 Received: from gecko.sbs.de ([194.138.37.40]:21080) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MPKQF-0004OQ-CH for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:02:12 -0400 Message-ID: <4A57821B.9010706@siemens.com> Date: Fri, 10 Jul 2009 20:02:03 +0200 From: Jan Kiszka MIME-Version: 1.0 Subject: Re: [Qemu-devel] Planning for the 0.11.0 release References: <4A401A65.3080804@us.ibm.com> <4A5771C3.7050103@siemens.com> <4A577465.1050104@us.ibm.com> <200907101840.55859.paul@codesourcery.com> In-Reply-To: <200907101840.55859.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paul Brook Cc: Mark McLoughlin , Anthony Liguori , qemu-devel@nongnu.org, kvm-devel , Markus Armbruster Paul Brook wrote: > The 32/64-bit switching is just plain wrong, and makes it absolutely > impossible for a client debugger to work correctly. As pointed out before, it doesn't break anything but adds a workaround for scenarios which are _now_ broken (16/32 bit target code exported as 64 bit is widely useless for gdb today). Sorry, but you never explained to me how user are _currently_ supposed to debug under that conditions, namely 16/32 bit code executed by qemu-system-x86_64. > If you really can't be bothered fixing gdb (and you *really* should), then it I do bother, but it's nothing for a long rainy afternoon. > should be some form of user switch that tells qemu to always report a 32-bit > register set. I could offer to add a monitor command so that one can additionally set/override the register representation during runtime that way. I do not see a use case for it based on all the scenarios I'm aware of or personally ran through the last year, but if it helps acceptance. However, only a command line switch locking down the mode would solve just half of the real-world problems. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux