diff options
| -rw-r--r-- | gdb/doc/ChangeLog | 6 | ||||
| -rw-r--r-- | gdb/doc/gdbint.texinfo | 9 |
2 files changed, 6 insertions, 9 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 953d769..409d219 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,9 @@ +2001-11-21 Jim Blandy <jimb@redhat.com> + + * gdbint.texinfo (TARGET_RANGE_PROFITABLE_FOR_HW_WATCHPOINT): + Delete documentation; this macro has been removed from the + sources. + 2001-11-13 Jim Blandy <jimb@redhat.com> * gdbint.texinfo (COERCE_FLOAT_TO_DOUBLE): Clarify. diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index bf16853..bab1523 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -446,15 +446,6 @@ used, e.g., on HP-UX which provides operations to disable and enable the page-level memory protection that implements hardware watchpoints on that platform. -@findex TARGET_RANGE_PROFITABLE_FOR_HW_WATCHPOINT -@item TARGET_RANGE_PROFITABLE_FOR_HW_WATCHPOINT (@var{pid},@var{start},@var{len}) -Some addresses may not be profitable to use hardware to watch, or may -be difficult to understand when the addressed object is out of scope, -and hence should not be watched with hardware watchpoints. On some -targets, this may have severe performance penalties, such that we -might as well use regular watchpoints, and save (possibly precious) -hardware watchpoints for other locations. - @findex target_insert_watchpoint @findex target_remove_watchpoint @item target_insert_watchpoint (@var{addr}, @var{len}, @var{type}) |