aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorNick Roberts <nickrob@snap.net.nz>2009-05-14 21:43:09 +0000
committerNick Roberts <nickrob@snap.net.nz>2009-05-14 21:43:09 +0000
commit508094de0161e10e83e5673c7ce17726a45e7ca1 (patch)
tree6a9b2b02e295d225c08bc98851546461c5a44d86 /gdb/doc
parent6718376f8fcff947f5d39a2d10162ed4486369a8 (diff)
downloadgdb-508094de0161e10e83e5673c7ce17726a45e7ca1.zip
gdb-508094de0161e10e83e5673c7ce17726a45e7ca1.tar.gz
gdb-508094de0161e10e83e5673c7ce17726a45e7ca1.tar.bz2
(GDB/MI General Design): Break up into four nodes.
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/gdb.texinfo10
1 files changed, 10 insertions, 0 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index f1b892d..0940790 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