From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1G3fpz-0000ia-Fh
	for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:13:39 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1G3fpx-0000gT-4M
	for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:13:38 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1G3fpw-0000gQ-Vh
	for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:13:37 -0400
Received: from [84.96.92.56] (helo=smTp.neuf.fr)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1G3fqD-0006wr-Il
	for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:13:53 -0400
Received: from [84.102.211.98] by sp604003mt.gpm.neuf.ld
	(Sun Java System Messaging Server 6.2-5.05 (built Feb 16 2006))
	with ESMTP id <0J2P002C7ZUPZ5S1@sp604003mt.gpm.neuf.ld> for
	qemu-devel@nongnu.org; Thu, 20 Jul 2006 23:04:01 +0200 (CEST)
Date: Thu, 20 Jul 2006 23:04:01 +0200
From: Fabrice Bellard <fabrice@bellard.org>
Subject: Re: [Qemu-devel] Trouble with GDB & Some 'Can it be done' Debugging
	questions
In-reply-to: <20060720191723.GA25347@nevyn.them.org>
Message-id: <44BFEFC1.7090206@bellard.org>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <BAY114-F38CDA81529C08CF233B723BD600@phx.gbl>
	<20060720191723.GA25347@nevyn.them.org>
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: qemu-devel@nongnu.org

Daniel Jacobowitz wrote:
> On Wed, Jul 19, 2006 at 08:43:57AM +0000, Steve Ellenoff wrote:
> 
>>#3) Anytime I try to dump the instruction at the current IP such as:
>>(gdb) x /10i $eip
>>
>>I get this - which means it's not actually reading or displaying the memory 
>>properly, since those look to be what you would see if it was all 0 in 
>>memory (or maybe it's all 0xff - whichever).l
>>
>>0xe05f: add    %al,(%eax)
> 
> 
> qemu doesn't report memory errors to GDB.  It reports -1 values
> instead.  This is annoying.  I think I posted a patch for it once and
> never followed up when it was ignored.

This is not correct: an error is correctly reported by the QEMU gdb stub...

Regards,

Fabrice.