aboutsummaryrefslogtreecommitdiff
path: root/gdb/doc
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-05-16 09:34:20 -0600
committerTom Tromey <tromey@adacore.com>2023-06-12 12:09:56 -0600
commit67efac36f17824b147b3d4645719404ccd662206 (patch)
treed31f11164e20dbf2507a991be2ffa9f6a5784485 /gdb/doc
parent8115dffa1e76ab007223199dfbc8c1298d2bf06e (diff)
downloadgdb-67efac36f17824b147b3d4645719404ccd662206.zip
gdb-67efac36f17824b147b3d4645719404ccd662206.tar.gz
gdb-67efac36f17824b147b3d4645719404ccd662206.tar.bz2
Add "target" parameter to DAP attach request
This adds a new "target" to the DAP attach request. This is passed to "target remote". I thought "attach" made the most sense for this, because in some sense gdb is attaching to a running process. It's worth noting that all DAP "attach" parameters are defined by the implementation. Reviewed-By: Eli Zaretskii <eliz@gnu.org>
Diffstat (limited to 'gdb/doc')
-rw-r--r--gdb/doc/gdb.texinfo8
1 files changed, 6 insertions, 2 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 5823bf2..fc3a330 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -39070,12 +39070,16 @@ If provided, this is a string that specifies the program to use. This
corresponds to the @code{file} command. @xref{Files}.
@end table
-@value{GDBN} defines a parameter that can be passed to the
-@code{attach} request:
+@value{GDBN} defines some parameters that can be passed to the
+@code{attach} request. One of these must be specified.
@table @code
@item pid
The process ID to which @value{GDBN} should attach. @xref{Attach}.
+
+@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}.
@end table
@node JIT Interface