This is the mail archive of the gdb-patches@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] |
Eli Zaretskii wrote:
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.
This for a not-yet-submitted remote target, called CRISv32.
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.
I have defined HAVE_NONSTEPPABLE_WATCHPOINT, to make GDB disable the watchpoint and step over it to evaluate it.
(In addition there is also one hardware instruction breakpoint, but I guess that doesn't matter in this context.)
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=967 http://sources.redhat.com/ml/gdb-patches/2002-09/msg00739.html
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |