This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] GDB patches for hw watchpoints - revised
- From: Daniel Jacobowitz <drow at false dot org>
- To: Wu Zhou <woodzltc at cn dot ibm dot com>
- Cc: gdb-patches at sources dot redhat dot com, mark dot kettenis at xs4all dot nl
- Date: Tue, 6 Dec 2005 15:28:48 -0500
- Subject: Re: [RFC] GDB patches for hw watchpoints - revised
- References: <Pine.LNX.4.63.0512061356530.10445@linux.site> <uslt6km76.fsf@gnu.org>
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 <woodzltc@cn.ibm.com>
> > 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