Re: [PATCH] gdb: use current executable for 'remote exec-file' in some cases

[Eli Zaretskii <eliz@gnu.org>]

> From: Andrew Burgess <aburgess@redhat.com>
> Cc: Andrew Burgess <aburgess@redhat.com>
> Date: Mon,  6 Oct 2025 16:07:50 +0100
> 
> diff --git a/gdb/NEWS b/gdb/NEWS
> index 2c73776944f..cfea3cf95c9 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -31,6 +31,13 @@
>    subsequent runs of the inferior will use the same arguments as the
>    first run.
>  
> +* When connected to an extended-remote target which does not have an
> +  executable specified, if the current executable is specified using a
> +  'target:' prefix; or if the sysroot does not have a 'target:'
> +  prefix, and the current executable is within the sysroot; then GDB
> +  can use the current executable name in order to start inferiors on
> +  the remote without having to 'set remote exec-file'.

This single sentence is quite a mouth-full.  Could you perhaps split
it into two or more simpler sentences, e.g., the first one describing
the capability and the rest describing the limitations/restrictions?

> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -24668,7 +24668,9 @@ Remote Configuration
>  Select the file used for @code{run} with @code{target
>  extended-remote}.  This should be set to a filename valid on the
>  target system.  If it is not set, the target will use a default
> -filename (e.g.@: the last program run).
> +filename (e.g.@: the last program run, or a filename derived from the
> +current executable if @value{GDBN} and the remote can see the same
> +file system).

This part is okay.

Thanks.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>