diff options
Diffstat (limited to 'gdb/doc')
| -rw-r--r-- | gdb/doc/ChangeLog | 10 | ||||
| -rw-r--r-- | gdb/doc/gdb.texinfo | 6 | ||||
| -rw-r--r-- | gdb/doc/gdbint.texinfo | 17 |
3 files changed, 32 insertions, 1 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 077da82..cfb80b4 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,13 @@ +1999-10-15 Kevin Buettner <kevinb@cygnus.com> + + * gdbint.texinfo (MEMORY_INSERT_BREAKPOINT, + MEMORY_REMOVE_BREAKPOINT): Document. + +Thu Oct 14 21:17:17 1999 Andrew Cagney <cagney@b1.cygnus.com> + + * gdb.texinfo (remote): Document how GDB ignores the qOffsets BSS + offset re-using the DATA offset instead. + 1999-10-11 Jim Kingdon <kingdon@redhat.com> * gdbint.texinfo (Target Architecture Definition): Add PARM_BOUNDARY. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 9a257e6..316d58c 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -9226,7 +9226,11 @@ digits). See @code{remote.c:parse_threadlist_response()}. @item query sect offs @tab @code{q}@code{Offsets} -@tab Get section offsets. +@tab +Get section offsets that the target used when re-locating the downloaded +image. @emph{Note: while a @code{Bss} offset is included in the +response, @value{GDBN} ignores this and instead applies the @code{Data} +offset to the @code{Bss} section.} @item @tab reply @code{Text=}@var{xxx}@code{;Data=}@var{yyy}@code{;Bss=}@var{zzz} diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index 0115375..25666c3 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -1239,6 +1239,23 @@ instruction of the architecture. Replaces all the other @var{BREAKPOINT} macros. +@item MEMORY_INSERT_BREAKPOINT (addr, contents_cache) +@item MEMORY_REMOVE_BREAKPOINT (addr, contents_cache) + +Insert or remove memory based breakpoints. Reasonable defaults +(@code{default_memory_insert_breakpoint} and +@code{default_memory_remove_breakpoint} respectively) have been +provided so that it is not necessary to define these for most +architectures. Architectures which may want to define +@var{MEMORY_INSERT_BREAKPOINT} and @var{MEMORY_REMOVE_BREAKPOINT} will +likely have instructions that are oddly sized or are not stored in a +conventional manner. + +It may also be desirable (from an efficiency standpoint) to define +custom breakpoint insertion and removal routines if +@var{BREAKPOINT_FROM_PC} needs to read the target's memory for some +reason. + @item CALL_DUMMY_P A C expresson that is non-zero when the target suports inferior function calls. |