* gdb.texinfo (Invoking GDB): Document --args.

	(Mode Options): Likewise.

2 files changed, 20 insertions, 0 deletions

diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index 409d219c181..97ab02d8b90 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,8 @@
+2001-11-21  Tom Tromey  <tromey@redhat.com>
+
+	* gdb.texinfo (Invoking GDB): Document --args.
+	(Mode Options): Likewise.
+
 2001-11-21  Jim Blandy  <jimb@redhat.com>
 
 	* gdbint.texinfo (TARGET_RANGE_PROFITABLE_FOR_HW_WATCHPOINT):
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index dec8be4bd36..4d55b7a59fe 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -752,6 +752,15 @@ debugger attached to a bare board, there may not be any notion of
 ``process'', and there is often no way to get a core dump.  @value{GDBN}
 will warn you if it is unable to attach or to read core dumps.
 
+You can optionally have @code{@value{GDBP}} pass any arguments after the
+executable file to the inferior using @code{--args}.  This option stops
+option processing.
+@example
+gdb --args gcc -O2 -c foo.c
+@end example
+This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set
+@code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}.
+
 You can run @code{@value{GDBP}} without printing the front material, which describes
 @value{GDBN}'s non-warranty, by specifying @code{-silent}:
 
@@ -1015,6 +1024,12 @@ uses the asynchronous event loop by default, unless disabled by the
 @cindex @code{--noasync}
 Disable the asynchronous event loop for the command-line interface.
 
+@item --args
+@cindex @code{--args}
+Change interpretation of command line so that arguments following the
+executable file are passed as command line arguments to the inferior.
+This option stops option processing.
+
 @item -baud @var{bps}
 @itemx -b @var{bps}
 @cindex @code{--baud}