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: Mark Kettenis <kettenis at chello dot nl>
- Cc: orjan dot friberg at axis dot com,gdb-patches at sources dot redhat dot com,drow at false dot org
- Date: 02 May 2004 07:49:23 +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>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> Date: Sat, 1 May 2004 23:17:35 +0200 (CEST)
> From: Mark Kettenis <kettenis@chello.nl>
>
> This patch breaks hardware watchpoints in SVR4-derived systems. Those
> systems don't provide target_stopped_data_address(). The default
> target_stopped_data_address() will always return zero
Then how do hardware watchpoints work on those systems? IIRC, without
a functional target_stopped_data_address, hardware watchpoints would
not really work, except by chance and only in simple cases. For
example, multiple watchpoints at the same address will not DTRT.
> Anyway. The problem is clearly that the whole target-specific
> interface for hardware watchpoints is a mess. We should really try to
> *design* a proper interface instead of continuing to tweak the
> existing interfaces.
Agreed.
> Any people interested in makeing a proposal?
I could try, but I need help: I need to know how hardware watchpoints
work on supported platforms, including remote ones. If global and
area maintainers could describe that for systems they know, I will try
to come up with a proposal.