From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9392 invoked by alias); 17 Feb 2006 22:12:39 -0000 Received: (qmail 9355 invoked by uid 22791); 17 Feb 2006 22:12:34 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Fri, 17 Feb 2006 22:12:31 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1FADpy-0000cv-7F; Fri, 17 Feb 2006 17:12:26 -0500 Date: Sat, 18 Feb 2006 10:56:00 -0000 From: Daniel Jacobowitz To: Paul Koning Cc: eliz@gnu.org, ghost@cs.msu.su, gdb@sources.redhat.com Subject: Re: MI: reporting of multiple breakpoints Message-ID: <20060217221226.GA2327@nevyn.them.org> Mail-Followup-To: Paul Koning , eliz@gnu.org, ghost@cs.msu.su, gdb@sources.redhat.com References: <17398.11182.747232.774924@gargle.gargle.HOWL> <20060217200712.GB30145@nevyn.them.org> <17398.12047.624911.347942@gargle.gargle.HOWL> <20060217202047.GC30881@nevyn.them.org> <17398.15554.431196.208031@gargle.gargle.HOWL> <20060217211942.GA609@nevyn.them.org> <17398.16942.92466.13879@gargle.gargle.HOWL> <20060217214303.GA1375@nevyn.them.org> <17398.18077.716159.385642@gargle.gargle.HOWL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17398.18077.716159.385642@gargle.gargle.HOWL> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00230.txt.bz2 On Fri, Feb 17, 2006 at 04:56:45PM -0500, Paul Koning wrote: > However, the fact that some architectures have imprecise watchpoints > is no reason to force imprecision on those that can do better. In > other words, this should be an example of target-dependent machinery: > if the target has the ability to determine the "PC of the watchpoint > trigger instruction" then it should do so, and the break/watch display > reporting machinery should use that information to report the > watchpoint at the "correct" source line. I am not familiar with any hardware watchpoint implementation (onboard registers, JTAG, whatever) that can supply "PC of the watchpoint trigger instruction" usefully. But I'm not familiar with a whole heck of a lot of those, so... Page table based watchpoints obviously could do this. On architectures with fixed size instructions and precise watchpoints and no delay slots, maybe you can get away with a subtraction, but I'm not at all sure about that. Hum, it looks like MIPS WatchHi/WatchLo can actually point to the instruction itself. But now we're off into wishlist land, I'm afraid. -- Daniel Jacobowitz CodeSourcery