From c1d43aa2307fbbf4b7fd79c28f55a94be8d14506 Mon Sep 17 00:00:00 2001 From: Roland Pesch Date: Wed, 6 Nov 1991 01:22:44 +0000 Subject: [PATCH] Correction in intro text re corefile arg (may also be procID); second time around didn't ack two possibilities. --- gdb/doc/gdb.texinfo | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 85f921d645e..8f6e9f27c2b 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -872,14 +872,15 @@ _fi__(!_GENERIC__) @subsection Choosing Files As shown above, any arguments other than options specify an executable -file and core file; that is, the first argument encountered with no -associated option flag is equivalent to a @samp{-se} option, and the -second, if any, is equivalent to a @samp{-c} option. Many options have -both long and short forms; both are shown here. The long forms are also -recognized if you truncate them, so long as enough of the option is -present to be unambiguous. (If you prefer, you can flag option -arguments with @samp{+} rather than @samp{-}, though we illustrate the -more usual convention.) +file and core file (or process ID); that is, the first argument +encountered with no associated option flag is equivalent to a @samp{-se} +option, and the second, if any, is equivalent to a @samp{-c} option if +it's the name of a file. +Many options have both long and short forms; both are shown here. The +long forms are also recognized if you truncate them, so long as enough +of the option is present to be unambiguous. (If you prefer, you can +flag option arguments with @samp{+} rather than @samp{-}, though we +illustrate the more usual convention.) @table @code @item -symbols=@var{file} -- 2.30.2