From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MPKjj-0002EG-LM
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:22:19 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MPKje-00022x-QJ
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:22:19 -0400
Received: from [199.232.76.173] (port=45060 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MPKje-00022q-L2
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:22:14 -0400
Received: from mx20.gnu.org ([199.232.41.8]:39787)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1MPKje-00084c-DE
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:22:14 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1MPKjd-0007Cu-BY
	for qemu-devel@nongnu.org; Fri, 10 Jul 2009 14:22:13 -0400
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 19:22:09 +0100
References: <4A401A65.3080804@us.ibm.com>
	<200907101840.55859.paul@codesourcery.com>
	<4A57821B.9010706@siemens.com>
In-Reply-To: <4A57821B.9010706@siemens.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907101922.10938.paul@codesourcery.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Anthony Liguori <aliguori@us.ibm.com>, Markus Armbruster <armbru@redhat.com>, kvm-devel <kvm@vger.kernel.org>, Mark McLoughlin <markmc@redhat.com>

> 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.

You're working around a gdb bug it in a way that means a fixed gdb can't 
possibly work.  IMO the cure is worse than the disease.  Changing the register 
set reported to gdb part way through a session will always break. There's no 
possible way for gdb to what state the target is going to be in until it 
actually queries it.

Paul