Doc update

Doc update

[Don Howard]

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

Re: Doc update

[Eli Zaretskii]

On Tue, 30 Oct 2001, Don Howard wrote:

> 2001-10-30  Don Howard  <dhoward@redhat.com>
> 
> 	* gdb.texinfo: Added documentation for the behavior of gdb with
> 	input redirected from a file.

Thanks!

This is approved, with the following comments:

> +@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.

The words "stdin", "stdout", and "stderr" should have a @code markup,
since they are C symbols.  In fact, it might be better to replace them
with "standard input" etc., since GDB is used for debugging languages
other than C, so a user might not know what `stdin' is.

> +@example
> +gdb < cmds > log 2>&1
> +@end example
> +
> +(The syntax above will vary depending on the shell used) This example

A period is missing inside the parens.

> +will execute commands from the file @var{cmds}. All output and errors
> +would be directed to @var{log}.

In this case, `cmds' and `log' are not metasyntactic variables, they
are simple file names.  So they should have the @file markup.

Oh, and in the ChangeLog entry, please tell in what node was the
change done, as if the node were a function (i.e. inside parens).

Re: Doc update

[Don Howard]

Ok to commit the following?


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

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


Index: gdb.texinfo
===================================================================
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/31 17:06:33
@@ -13114,6 +13114,20 @@ 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 standard input.  In this
+mode, normal output goes to standard output and error output goes to
+standard error.  Errors in a command file supplied on standard input 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 @file{cmds}. All output and errors
+would be directed to @file{log}.
+
 @node Output
 @section Commands for controlled output


-- 
-Don
dhoward@redhat.com
gdb engineering

Re: Doc update

[Eli Zaretskii]

> Date: Wed, 31 Oct 2001 09:45:39 -0800 (PST)
> From: Don Howard <dhoward@redhat.com>
> 
> Ok to commit the following?

Yes.  But please use 3 dashes in a row, `---', in this line:

> +not terminate execution of the command file -- execution continues with

Sorry if I missed that earlier.

Re: Doc update

[Don Howard]

On Wed, 31 Oct 2001, Eli Zaretskii wrote:

> > Date: Wed, 31 Oct 2001 09:45:39 -0800 (PST)
> > From: Don Howard <dhoward@redhat.com>
> >
> > Ok to commit the following?
>
> Yes.  But please use 3 dashes in a row, `---', in this line:
>
> > +not terminate execution of the command file -- execution continues with
>
> Sorry if I missed that earlier.
>


Committed.


-- 
-Don
dhoward@redhat.com
gdb engineering