Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT
Eli Zaretskii
eliz@gnu.org
Sun May 2 04:48:00 GMT 2004
> 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.
More information about the Gdb-patches
mailing list