From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G3g6k-0005Jo-9S for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:30:58 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G3g6i-0005JY-Pe for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:30:58 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G3g6i-0005JV-MW for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:30:56 -0400 Received: from [66.93.172.17] (helo=nevyn.them.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1G3g6z-0007wx-Ah for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:31:13 -0400 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1G3g6h-0007c0-Jw for qemu-devel@nongnu.org; Thu, 20 Jul 2006 17:30:55 -0400 Date: Thu, 20 Jul 2006 17:30:55 -0400 From: Daniel Jacobowitz Subject: Re: [Qemu-devel] Trouble with GDB & Some 'Can it be done' Debugging questions Message-ID: <20060720213055.GA29241@nevyn.them.org> References: <20060720191723.GA25347@nevyn.them.org> <44BFEFC1.7090206@bellard.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44BFEFC1.7090206@bellard.org> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Thu, Jul 20, 2006 at 11:04:01PM +0200, Fabrice Bellard wrote: > 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... Must've been fixed then! Sorry. In that case, Steve, you're probably reading the wrong address (maybe segmentation-related?). -- Daniel Jacobowitz CodeSourcery