Re: Display of read/access watchpoints when HAVE_NONSTEPPABLE_WATCHPOINT

[Orjan Friberg <orjan.friberg@axis.com>]

Eli Zaretskii wrote:
> 
> Perhaps none of the targets that support hardware read and access
> watchpoints define HAVE_NONSTEPPABLE_WATCHPOINT?

Yes, that seems to be the case.

> Anyway, from your description, it is quite clear that if a target
> defines HAVE_NONSTEPPABLE_WATCHPOINT, GDB must call
> target_stopped_data_address before it disables the watchpoint and
> steps over it, or else the target end should store the necessary info
> somewhere and deliver it when target_stopped_data_address is called.

Right.  I was thinking I could make watchpoints "steppable" by disabling 
them in the remote stub when a watchpoint hits, and then enabling them 
again when a continue is issued, but it feels like that might create 
more problems than it solves.  (For example, watchpoints would never hit 
when single-stepping.)

I'll see if I can understand enough of handle_inferior_event to whip up 
a patch for either of your suggestions.  Thanks for your answer.

-- 
Orjan Friberg
Axis Communications