From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-ID: <200907101922.10938.paul@codesourcery.com>
References: <4A401A65.3080804@us.ibm.com> <200907101840.55859.paul@codesourcery.com> <4A57821B.9010706@siemens.com>
Mime-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Mark McLoughlin <markmc@redhat.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	"kvm-devel" <kvm@vger.kernel.org>,
	Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.codesourcery.com ([65.74.133.4]:39751 "EHLO
	mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752750AbZGJSWN (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 10 Jul 2009 14:22:13 -0400
In-Reply-To: <4A57821B.9010706@siemens.com>
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

> 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