This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT
- From: "Eli Zaretskii" <eliz at gnu dot org>
- To: Orjan Friberg <orjan dot friberg at axis dot com>
- Cc: kettenis at chello dot nl, gdb-patches at sources dot redhat dot com, drow at false dot org
- Date: Mon, 03 May 2004 20:48:32 +0200
- Subject: Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT
- References: <ur81oqb1c.fsf@elta.co.il> <407282F4.2080602@axis.com> <20040406142228.GA29473@nevyn.them.org> <6654-Thu15Apr2004111217+0300-eliz@gnu.org> <407E8CEF.2050007@axis.com> <407FC69A.1000701@axis.com> <1438-Sat17Apr2004112204+0300-eliz@gnu.org> <4083E930.8040005@axis.com> <4087DFB6.1030801@axis.com> <200405012117.i41LHZSR001291@elgar.kettenis.dyndns.org> <ur7u3e5uk.fsf@gnu.org> <40962BF0.3030707@axis.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Mon, 03 May 2004 13:24:32 +0200
> From: Orjan Friberg <orjan.friberg@axis.com>
>
> This for a not-yet-submitted remote target, called CRISv32.
Thanks!
> It has 6 hardware data watchpoints, configurable as read/write or both
> (i.e. access). There are no alignment or length restriction on the
> memory regions that are watched.
>
> When a watchpoint hits, an exception register tells which watchpoints
> that triggered, and whether they trigged on read or write.
So this target could relatively easily support an API where the target
itself tells GDB which of watchpoints triggered and why, provided that
we invent a way for GDB to map between its watchpoint numbers and the
target-size hardware data watchpoints. Is that true?
> (In addition there is also one hardware instruction breakpoint, but I
> guess that doesn't matter in this context.)
Used for hardware-assisted breakpoints, yes?