diff options
author | Ulrich Weigand <uweigand@de.ibm.com> | 2007-06-13 17:38:43 +0000 |
---|---|---|
committer | Ulrich Weigand <uweigand@de.ibm.com> | 2007-06-13 17:38:43 +0000 |
commit | 3b3b875c482fe05ec3e51b31124b21433fee2ce9 (patch) | |
tree | 772cf8b25ef9f498a798d14d899f62271bd9de8c /gdb/breakpoint.h | |
parent | 819844ad98d84ef944ff721239ba2b55c2a34061 (diff) | |
download | gdb-3b3b875c482fe05ec3e51b31124b21433fee2ce9.zip gdb-3b3b875c482fe05ec3e51b31124b21433fee2ce9.tar.gz gdb-3b3b875c482fe05ec3e51b31124b21433fee2ce9.tar.bz2 |
2007-06-13 Markus Deuling <deuling@de.ibm.com>
* gdbarch.sh (BREAKPOINT_FROM_PC): Replace by
gdbarch_breakpoint_from_pc.
* s390-tdep.c (s390_gdbarch_init): Likewise (comment).
* remote.c (remote_insert_breakpoint)
(remote_insert_hw_breakpoint): Likewise.
* ppc-linux-tdep.c (ppc_linux_memory_remove_breakpoint): Likewise.
* mips-tdep.c (mips_breakpoint_from_pc): Likewise (comment).
* breakpoint.h (bp_target_info): Likewise (comment).
* breakpoint.c (read_memory_nobpt): Likewise.
* mem-break.c (default_memory_insert_breakpoint): Likewise.
(symtab.h, breakpoint.h): Remove include. Remove unnecessary comment.
* gdbarch.c, gdbarch.h: Regenerate.
Diffstat (limited to 'gdb/breakpoint.h')
-rw-r--r-- | gdb/breakpoint.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/breakpoint.h b/gdb/breakpoint.h index 6a28b79..1573ac8 100644 --- a/gdb/breakpoint.h +++ b/gdb/breakpoint.h @@ -188,7 +188,7 @@ struct bp_target_info { /* Address at which the breakpoint was placed. This is normally the same as ADDRESS from the bp_location, except when adjustment - happens in BREAKPOINT_FROM_PC. The most common form of + happens in gdbarch_breakpoint_from_pc. The most common form of adjustment is stripping an alternate ISA marker from the PC which is used to determine the type of breakpoint to insert. */ CORE_ADDR placed_address; @@ -203,7 +203,7 @@ struct bp_target_info int shadow_len; /* The size of the placed breakpoint, according to - BREAKPOINT_FROM_PC, when the breakpoint was inserted. This is + gdbarch_breakpoint_from_pc, when the breakpoint was inserted. This is generally the same as SHADOW_LEN, unless we did not need to read from the target to implement the memory breakpoint (e.g. if a remote stub handled the details). We may still |