Re: RFC: GDB as a loader 2/3: return child result

[Andrew STUBBS <andrew.stubbs@st.com>]

[-- Attachment #1: Type: text/plain, Size: 77 bytes --]

Here is a documentation patch to go with the original patch.

Andrew Stubbs


[-- Attachment #2: return-result-docs.patch --]
[-- Type: text/plain, Size: 1051 bytes --]

2005-10-28  Andrew Stubbs  <andrew.stubbs@st.com>

	* gdb.texinfo (Choosing modes): Add --return-child-result.


Index: src/gdb/doc/gdb.texinfo
===================================================================
--- src.orig/gdb/doc/gdb.texinfo	2005-10-28 10:37:07.000000000 +0100
+++ src/gdb/doc/gdb.texinfo	2005-10-28 11:35:18.000000000 +0100
@@ -1006,6 +1006,16 @@ This is particularly useful when using t
 Note that targets that give their output via @value{GDBN}, as opposed to
 writing directly to @code{stdout}, will also be made silent.
 
+@item -return-child-result
+@cindex @code{--return-child-result}
+The return code from @value{GDBN} will be the return code from the child
+process (the process being debugged), unless an error occurs or the user
+quits with an explicit value, such as @samp{quit 1}, for example.
+
+This is useful in conjunction with @samp{-batch} or @samp{-batch-silent},
+when @value{GDBN} is being used as a remote program loader or simulator
+interface.
+
 @item -nowindows
 @itemx -nw
 @cindex @code{--nowindows}