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

	* gdb.texinfo (overlays): Change @var(_ovly_debug_event)
	to @code(_ovly_debug_event).

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index f648cc2..f3a0fcf 100644 (file)
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2002-02-07  Michael Snyder  <msnyder@redhat.com>
+
+       * gdb.texinfo (overlays): Change @var(_ovly_debug_event)
+       to @code(_ovly_debug_event).
+
 2002-02-07  Andrew Cagney  <ac131313@redhat.com>
 
        * gdb.texinfo (How Overlays Work): Shrink the overlay diagram.

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 1f6634c..ed1fbc4 100644 (file)
--- 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