From: Nick Roberts <nickrob@snap.net.nz>
Date: Thu, 14 May 2009 21:43:09 +0000 (+0000)
Subject: (GDB/MI General Design): Break up into four nodes.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=508094de0161e10e83e5673c7ce17726a45e7ca1;p=binutils-gdb.git

(GDB/MI General Design): Break up into four nodes.
---

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index f1b892de7b0..09407900e02 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -19834,6 +19834,14 @@ processed.  Therefore, whenever an MI command results in an error,
 we recommend that the frontend refreshes all the information shown in 
 the user interface.
 
+
+@menu
+* Context management::
+* Asynchronous and non-stop modes::
+* Thread groups::
+@end menu
+
+@node Context management
 @subsection Context management
 
 In most cases when @value{GDBN} accesses the target, this access is
@@ -19886,6 +19894,7 @@ all subsequent commands.  No frontend is known to do this exactly
 right, so it is suggested to just always pass the @samp{--thread} and
 @samp{--frame} options.
 
+@node Asynchronous and non-stop modes
 @subsection Asynchronous command execution and non-stop mode
 
 On some targets, @value{GDBN} is capable of processing MI commands
@@ -19921,6 +19930,7 @@ highly target dependent.  However, the two commands
 @code{-exec-interrupt}, to stop a thread, and @code{-thread-info},
 to find the state of a thread, will always work.
 
+@node Thread groups
 @subsection Thread groups
 @value{GDBN} may be used to debug several processes at the same time.
 On some platfroms, @value{GDBN} may support debugging of several