Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Don Howard <dhoward@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: <gdb-patches@sources.redhat.com>
Subject: Re: Doc update
Date: Wed, 31 Oct 2001 09:49:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0110310856440.19444-100000@theotherone> (raw)
In-Reply-To: <Pine.SUN.3.91.1011031135953.7776J-100000@is>

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


  reply	other threads:[~2001-10-31  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30 13:27 Don Howard
2001-10-31  4:00 ` Eli Zaretskii
2001-10-31  9:49   ` Don Howard [this message]
2001-10-31 10:47     ` Eli Zaretskii
2001-10-31 11:21       ` Don Howard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.33.0110310856440.19444-100000@theotherone \
    --to=dhoward@redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox