From eb6476e2db406ba323efba438b0d1851e86d02e5 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Thu, 7 Dec 2023 09:51:52 -0700 Subject: 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 --- gdb/doc/gdb.texinfo | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) (limited to 'gdb/doc') 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}. -- cgit v1.1