2002-02-06 Michael Snyder <msnyder@redhat.com>

	* gdb.texinfo (overlays): Mention new magic symbol
	'_ovly_debug_event', which allows GDB to keep better track
	of overlays.

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 3959c6bf91eba447787af280ed1eee762bdbb0e8..891851c0796c3c5850a98c981723b56119a43598 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,9 @@
+2002-02-06  Michael Snyder  <msnyder@redhat.com>
+
+       * gdb.texinfo (overlays): Mention new magic symbol
+       '_ovly_debug_event', which allows GDB to keep better track
+       of overlays.
+
 2002-02-03  Eli Zaretskii  <eliz@is.elta.co.il>
 
        * gdb.texinfo (Memory Region Attributes): Fix the wording.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 260d2f1c1abb478b12506b841f3d5ebbba4cc312..902d7653caf59992981f357dfaca9d348f06c373 100644 (file)
--- 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