From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1IXw6E-0004om-74
	for qemu-devel@nongnu.org; Wed, 19 Sep 2007 05:44:02 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1IXw6B-0004o1-RV
	for qemu-devel@nongnu.org; Wed, 19 Sep 2007 05:44:01 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1IXw6B-0004nn-6r
	for qemu-devel@nongnu.org; Wed, 19 Sep 2007 05:43:59 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.60)
	(envelope-from <Johannes.Schindelin@gmx.de>) id 1IXw6A-0002yw-Ms
	for qemu-devel@nongnu.org; Wed, 19 Sep 2007 05:43:59 -0400
Date: Wed, 19 Sep 2007 10:43:04 +0100 (BST)
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [Qemu-devel] Mips guest
In-Reply-To: <46F0EA2E.2080609@bandsman.co.uk>
Message-ID: <Pine.LNX.4.64.0709191037140.28395@racer.site>
References: <46F0EA2E.2080609@bandsman.co.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: qemu-devel@nongnu.org
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: Nigel Horne <njh@bandsman.co.uk>
Cc: qemu-devel@nongnu.org

Hi,

On Wed, 19 Sep 2007, Nigel Horne wrote:

> The latest CVS snapshot has broken MIPS emulation.
> 
> [...]
>
> Then it hangs.
> 
> The last time I tried this guest was a couple of weeks ago, or so, and 
> all was fine then.

It would be so good if you could bisect this.

If you have git, clone qemu from git://git.kernel.dk/data/git/qemu.git, 
and use something "git log" to identify a commit that is likely to be 
good.  The easiest way to proceed is then to copy the commit name (this 
40-character hex string), and use it in

	git bisect start
	git bisect good <that-string>
	git bisect bad HEAD

It will find the middle point between the two, which you should compile 
and test.  Depending on the outcome of the test, you should mark the 
current commit as "git bisect good" or "git bisect bad" (you do not need 
to say which commit, if it is the current you mean).

Eventually, this procedure will give you the bad commit, which then makes 
it easier to see what actually broke the MIPS guest for you.

Thanks,
Dscho