From 81d4647008f8d3b66ae5dacf985d7f887294e231 Mon Sep 17 00:00:00 2001 From: Michael Snyder Date: Wed, 6 Feb 2002 18:29:38 +0000 Subject: [PATCH] 2002-02-06 Michael Snyder * gdb.texinfo (overlays): Mention new magic symbol '_ovly_debug_event', which allows GDB to keep better track of overlays. --- gdb/doc/ChangeLog | 6 ++++++ gdb/doc/gdb.texinfo | 9 +++++++++ 2 files changed, 15 insertions(+) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index 3959c6bf91e..891851c0796 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,9 @@ +2002-02-06 Michael Snyder + + * gdb.texinfo (overlays): Mention new magic symbol + '_ovly_debug_event', which allows GDB to keep better track + of overlays. + 2002-02-03 Eli Zaretskii * gdb.texinfo (Memory Region Attributes): Fix the wording. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 260d2f1c1ab..902d7653caf 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -6646,6 +6646,15 @@ executable file. When @value{GDBN} finds a matching entry, it consults the entry's @code{mapped} member to determine whether the overlay is currently mapped. +In addition, your overlay manager may define a function called +@var{_ovly_debug_event}. If this function is defined, @value{GDBN} +will silently set a breakpoint there. If the overlay manager then +calls this function whenever it has changed the overlay table, this +will enable @value{GDBN} to accurately keep track of which overlays +are in program memory, and update any breakpoints that may be set +in overlays. This will allow breakpoints to work even if the +overlays are kept in ROM or other non-writable memory while they +are not being executed. @node Overlay Sample Program @section Overlay Sample Program -- 2.30.2