aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-12-07 09:51:52 -0700
committerTom Tromey <tromey@adacore.com>2023-12-22 09:05:17 -0700
commiteb6476e2db406ba323efba438b0d1851e86d02e5 (patch)
tree8887453aacc110380b5b0a7423160a229999bd04 /gdb/doc
parent401b5b00ecef262ce36a8810775087c7d9928900 (diff)
downloadgdb-eb6476e2db406ba323efba438b0d1851e86d02e5.zip
gdb-eb6476e2db406ba323efba438b0d1851e86d02e5.tar.gz
gdb-eb6476e2db406ba323efba438b0d1851e86d02e5.tar.bz2
Add 'program' to DAP 'attach' request
In many cases, it's not possible for gdb to discover the executable when a DAP 'attach' request is used. This patch lets the IDE supply this information. Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/gdb.texinfo11
1 files changed, 10 insertions, 1 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 7a5d357..3cb7682 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -39603,12 +39603,21 @@ the same approach as the @code{start} command. @xref{Starting}.
@end table
@value{GDBN} defines some parameters that can be passed to the
-@code{attach} request. One of these must be specified.
+@code{attach} request. Either @code{pid} or @code{target} must be
+specified, but if both are specified then @code{target} will be
+ignored.
@table @code
@item pid
The process ID to which @value{GDBN} should attach. @xref{Attach}.
+@item program
+If provided, this is a string that specifies the program to use. This
+corresponds to the @code{file} command. @xref{Files}. In some cases,
+@value{GDBN} can automatically determine which program is running.
+However, for many remote targets, this is not the case, and so this
+should be supplied.
+
@item target
The target to which @value{GDBN} should connect. This is a string and
is passed to the @code{target remote} command. @xref{Connecting}.