diff options
| author | Andreas Schwab <schwab@linux-m68k.org> | 2008-05-02 11:07:25 +0000 |
|---|---|---|
| committer | Andreas Schwab <schwab@linux-m68k.org> | 2008-05-02 11:07:25 +0000 |
| commit | 5009afc5ba7a0d57f28fbc834757145fe1f45549 (patch) | |
| tree | 84eb99d8f3cee40602e1f5f48650b3db51714cc4 /gdb/doc/gdbint.texinfo | |
| parent | a99f88dcfcd4f977edc6daf5c469d656808e5576 (diff) | |
| download | gdb-5009afc5ba7a0d57f28fbc834757145fe1f45549.zip gdb-5009afc5ba7a0d57f28fbc834757145fe1f45549.tar.gz gdb-5009afc5ba7a0d57f28fbc834757145fe1f45549.tar.bz2 | |
* target.h (struct target_ops): Add
to_watchpoint_addr_within_range.
(target_watchpoint_addr_within_range): New function.
* target.c (update_current_target): Inherit
to_watchpoint_addr_within_range, defaulting to
default_watchpoint_addr_within_range.
(default_watchpoint_addr_within_range): New function.
(debug_to_watchpoint_addr_within_range): New function.
(setup_target_debug): Set to_watchpoint_addr_within_range.
* ppc-linux-nat.c (ppc_linux_watchpoint_addr_within_range):
New function.
(_initialize_ppc_linux_nat): Set to_watchpoint_addr_within_range.
* breakpoint.c (watchpoints_triggered): Use
target_watchpoint_addr_within_range.
* gdbint.texinfo (Algorithms): Describe
target_watchpoint_addr_within_range.
Diffstat (limited to 'gdb/doc/gdbint.texinfo')
| -rw-r--r-- | gdb/doc/gdbint.texinfo | 13 |
1 files changed, 11 insertions, 2 deletions
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index 39cb031..d020f5b 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -9,7 +9,7 @@ @ifinfo This file documents the internals of the GNU debugger @value{GDBN}. Copyright (C) 1990, 1991, 1992, 1993, 1994, 1996, 1998, 1999, 2000, 2001, - 2002, 2003, 2004, 2005, 2006 + 2002, 2003, 2004, 2005, 2006, 2008 Free Software Foundation, Inc. Contributed by Cygnus Solutions. Written by John Gilmore. Second Edition by Stan Shebs. @@ -711,10 +711,19 @@ target's watchpoint indication is sticky, i.e., stays set after resuming, this method should clear it. For instance, the x86 debug control register has sticky triggered flags. +@findex target_watchpoint_addr_within_range +@item target_watchpoint_addr_within_range (@var{target}, @var{addr}, @var{start}, @var{length}) +Check whether @var{addr} (as returned by @code{target_stopped_data_address}) +lies within the hardware-defined watchpoint region described by +@var{start} and @var{length}. This only needs to be provided if the +granularity of a watchpoint is greater than one byte, i.e., if the +watchpoint can also trigger on nearby addresses outside of the watched +region. + @findex HAVE_STEPPABLE_WATCHPOINT @item HAVE_STEPPABLE_WATCHPOINT If defined to a non-zero value, it is not necessary to disable a -watchpoint to step over it. Like @code{gdbarch_have_nonsteppable_watchpoint}, +watchpoint to step over it. Like @code{gdbarch_have_nonsteppable_watchpoint}, this is usually set when watchpoints trigger at the instruction which will perform an interesting read or write. It should be set if there is a temporary disable bit which allows the processor |