From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30912 invoked by alias); 6 Dec 2005 20:28:53 -0000 Received: (qmail 30899 invoked by uid 22791); 6 Dec 2005 20:28:53 -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; Tue, 06 Dec 2005 20:28:51 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EjjQe-0002VV-Uv; Tue, 06 Dec 2005 15:28:49 -0500 Date: Tue, 06 Dec 2005 23:31:00 -0000 From: Daniel Jacobowitz To: Wu Zhou Cc: gdb-patches@sources.redhat.com, mark.kettenis@xs4all.nl Subject: Re: [RFC] GDB patches for hw watchpoints - revised Message-ID: <20051206202848.GA9568@nevyn.them.org> Mail-Followup-To: Wu Zhou , gdb-patches@sources.redhat.com, mark.kettenis@xs4all.nl References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00119.txt.bz2 On Tue, Dec 06, 2005 at 10:25:01PM +0200, Eli Zaretskii wrote: > > Date: Tue, 6 Dec 2005 14:12:26 +0800 (CST) > > From: Wu Zhou > > cc: drow@false.org, eliz@gnu.org, mark.kettenis@xs4all.nl > > > > 3. Eli ever expressed a concern that the PPC doesn't have a way to return > > the data address that triggered the watchpoint? As far as I think, the > > reason is that PPC will only have one DABR (if it does have). So maybe we > > don't need to have such a method. > > Sorry, I'm not following: no matter how many debug registers the PPC > has, it can still return to GDB the data address that triggered the > watchpoint. I don't think the higher levels of GDB (breakpoint.c) > should know or assume anything about the target capabilities or > resources. Let's try keeping the code clean of such peculiarities. Wu, you're using GETSIGINFO to check for a watchpoint. Then isn't the faulting address stored in the siginfo anyway? -- Daniel Jacobowitz CodeSourcery, LLC