This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: TARGET_REGION_OK_FOR_HW_WATCHPOINT in target vector


Date: Thu, 19 Sep 2002 21:39:29 -0400
From: Andrew Cagney <ac131313@ges.redhat.com>

The macro TARGET_REGION_OK_FOR_HW_WATCHPOINT() needs to be moved to the target vector.

Yes.


As part of this, I'd like to propose that its behavour be modified slightly. Instead of returning non-zero to indicate that the vaddr:len is ok, it return the number of h/w watchpoint resources that are needed to watch vaddr:len.

I don't see any problem with that change.  But do we really need it?
That is, where would this new functionality be used?
I know of an architecture (need to find out if it is public) where some addr:len pairs require more than a single watch resource. Without it, the target would assume that every watchpoint is a worst case (needing max resources) and count accordingly.

Andrew



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]