import gdb-1999-08-09 snapshot

4 files changed, 60 insertions, 4 deletions

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index a6507bd..2d0b2ee 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,16 @@
+1999-08-06  Tom Tromey  <tromey@cygnus.com>
+
+	* gdb.texinfo (KOD): New node.
+
+Fri Aug  6 17:05:48 1999  Andrew Cagney  <cagney@b1.cygnus.com>
+
+	* remote.texi (Rcmd): Fix minor formatting typos.
+
+Thu Aug  5 17:57:41 1999  Andrew Cagney  <cagney@b1.cygnus.com>
+
+	* remote.texi (protocol qRcmd): Allow ``OK'' and ``O...'' response
+ 	packets.
+
 1999-07-14  Jim Blandy  <jimb@zwingli.cygnus.com>
 
 	* gdbint.texinfo (PREPARE_TO_PROCEED, ADDR_BITS_REMOVE): Doc
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index fec3571..92e4a21 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -8325,6 +8325,7 @@ targets}).
 * Target Commands::             Commands for managing targets
 * Byte Order::                  Choosing target byte order
 * Remote::                      Remote debugging
+* KOD::                         Kernel Object Display
 
 @end menu
 
@@ -8703,7 +8704,7 @@ Note that these commands merely adjust interpretation of symbolic
 data on the host, and that they have absolutely no effect on the
 target system.
 
-@node Remote,  , Byte Order, Targets
+@node Remote, KOD, Byte Order, Targets
 @section Remote debugging
 @cindex remote debugging
 
@@ -8742,6 +8743,44 @@ configuration of @value{GDBN}; use @code{help target} to list them.
 @include remote.texi
 
 
+@node KOD,  , Remote, Targets
+@section Kernel Object Display
+@cindex kernel object display
+@cindex kernel object
+@cindex KOD
+
+Some targets support kernel object display.  Using this facility,
+@value{GDBN} communicates specially with the underlying operating system
+and can display information about operating system-level objects such as
+mutexes and other synchronization objects.  Exactly which objects can be
+displayed is determined on a per-OS basis.
+
+Use the @code{set os} command to set the operating system.  This tells
+@value{GDBN} which kernel object display module to initialize:
+
+@example
+(gdb) set os cisco
+@end example
+
+If @code{set os} succeeds, @value{GDBN} will display some information
+about the operating system, and will create a new @code{info} command
+which can be used to query the target.  The @code{info} command is named
+after the operating system:
+
+@example
+(gdb) info cisco
+List of Cisco Kernel Objects
+Object     Description
+any        Any and all objects
+@end example
+
+Further subcommands can be used to query about particular objects known
+by the kernel.
+
+There is currently no way to determine whether a given operating system
+is supported other than to try it.
+
+
 @node Controlling GDB
 @chapter Controlling @value{GDBN}
 
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index a94fcc4..1dfd133 100644
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -361,7 +361,7 @@ command), and it can also read more symbols via the ``add-file'' and
 
 Symbol files are initially opened by code in @file{symfile.c} using the
 BFD library.  BFD identifies the type of the file by examining its
-header.  @code{symfile_init} then uses this identification to locate a
+header.  @code{find_sym_fns} then uses this identification to locate a
 set of symbol-reading functions.
 
 Symbol reading modules identify themselves to GDB by calling
diff --git a/gdb/doc/remote.texi b/gdb/doc/remote.texi
index 7b3c057..d8636da 100644
--- a/gdb/doc/remote.texi
+++ b/gdb/doc/remote.texi
@@ -770,9 +770,13 @@ See @code{remote.c:remote_unpack_thread_info_response()}.
 execution.  @emph{Implementors should note that providing access to a
 stubs's interpreter may have security implications}.
 @item
-@tab reply @var{OUTPUT}
+@tab reply @var{OUTPUT} or @code{OK}
 @tab
-The @var{OUTPUT} (hex encoded).  Must be non-empty.
+The @var{OUTPUT} is the hex encoded output from the command.  @code{OK}
+is returned when the @var{OUTPUT} would have been empty.  The target may
+also respond with a number of intermediate @code{O}@var{OUTPUT} console
+output packets.
+
 @item
 @tab reply @samp{}
 @tab