Doc update

[Don Howard <dhoward@redhat.com>]

The gdb manual doesn't seem to mention that you can supply a command
script on stdin (Correct me if it's there and I've missed it).



2001-10-30  Don Howard  <dhoward@redhat.com>

	* gdb.texinfo: Added documentation for the behavior of gdb with
	input redirected from a file.




RCS file: /cvs/src/src/gdb/doc/gdb.texinfo,v
retrieving revision 1.52
diff -p -u -w -r1.52 gdb.texinfo
--- gdb.texinfo 2001/10/30 04:05:36     1.52
+++ gdb.texinfo 2001/10/30 21:05:19
@@ -13114,6 +13114,19 @@ without asking when used in a command fi
 normally print messages to say what they are doing omit the messages
 when called from command files.

+@value{GDBN} also accepts command input from stdin.  In this mode,
+normal output goes to stdout and error output goes to stderr.  Errors in
+a command file supplied on stdin do not terminate execution of the
+command file -- execution continues with the next command.
+
+@example
+gdb < cmds > log 2>&1
+@end example
+
+(The syntax above will vary depending on the shell used) This example
+will execute commands from the file @var{cmds}. All output and errors
+would be directed to @var{log}.
+
 @node Output
 @section Commands for controlled output

-- 
-Don
dhoward@redhat.com
gdb engineering