From def71bfa3c2aaf973c269d5efb4d3b71e4b39416 Mon Sep 17 00:00:00 2001 From: Michael Snyder Date: Fri, 8 Feb 2002 00:39:45 +0000 Subject: [PATCH] 2002-02-07 Michael Snyder * gdb.texinfo (overlays): Change @var(_ovly_debug_event) to @code(_ovly_debug_event). --- gdb/doc/ChangeLog | 5 +++++ gdb/doc/gdb.texinfo | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index f648cc293e4..f3a0fcfda7c 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2002-02-07 Michael Snyder + + * gdb.texinfo (overlays): Change @var(_ovly_debug_event) + to @code(_ovly_debug_event). + 2002-02-07 Andrew Cagney * gdb.texinfo (How Overlays Work): Shrink the overlay diagram. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 1f6634c11d7..ed1fbc4134a 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -6651,7 +6651,7 @@ 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} +@code{_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 -- 2.30.2