From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K2mpw-0005Dl-5b for qemu-devel@nongnu.org; Sun, 01 Jun 2008 08:39:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K2mps-0005AG-1U for qemu-devel@nongnu.org; Sun, 01 Jun 2008 08:38:57 -0400 Received: from [199.232.76.173] (port=45215 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K2mpr-0005A2-Os for qemu-devel@nongnu.org; Sun, 01 Jun 2008 08:38:55 -0400 Received: from mail2.shareable.org ([80.68.89.115]:41502) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K2mpr-0001Cv-IR for qemu-devel@nongnu.org; Sun, 01 Jun 2008 08:38:55 -0400 Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from ) id 1K2mpo-00016t-Up for qemu-devel@nongnu.org; Sun, 01 Jun 2008 13:38:52 +0100 Date: Sun, 1 Jun 2008 13:38:52 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 0/5] Debugger enhancements Message-ID: <20080601123852.GB3687@shareable.org> References: <48414AC8.7080206@web.de> <484181C4.6080002@bellard.org> <200805311805.03739.paul@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200805311805.03739.paul@codesourcery.com> 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 Paul Brook wrote: > On most targets watchpoint traps occur after the instruction > completes, so you have to defer the DEBUG exception. Normal MMU > faults occur before the instruction completes. Ok. It might be a useful architecture-independent debugging feature to _also_ have the ability to trap a watchpoint before the memory access though - especially writes. Are there any tracing tools which use the gdbstub support and could make use of that? Can GDB make use of that? -- Jamie