On Wed, Aug 16, 2023 at 5:56 PM Andrew Burgess via Gdb-patches <
gdb-patches@sourceware.org> wrote:

> The current behaviour for 'show remote exec-file' is this:
>
>   (gdb) show remote exec-file
>
>   (gdb) set remote exec-file /abc
>   (gdb) show remote exec-file
>   /abc
>   (gdb)
>
> The first output, the blank line, is just GDB showing the default
> empty value.
>
> This output is not really inline with GDB's more full sentence style
> output, so in this commit I've updated things, the output is now:
>
>   (gdb) show remote exec-file
>   The remote exec-file is unset, the default remote executable will be
> used.
>   (gdb) set remote exec-file /abc
>   (gdb) show remote exec-file
>   The remote exec-file is "/abc".
>   (gdb)
>
> Which I think is more helpful to the user.
>
> I have also updated the help text for this setting.  Previously we had
> a set/show header line, but no body text, now we have:
>
>   (gdb) help show remote exec-file
>   Show the remote pathname for starting inferiors.
>   This is the path, on the remote target, used when starting an inferior,
>   for example with the "run", "start", or "starti" commands.
>   This setting is only useful when debugging a remote target, otherwise,
>   this setting is not used.
>   (gdb)
>
> Which is hopefully more helpful.
>
>
I really like the change in behaviour. Showing the blank line for the
default remote exec-file is confusing. The more verbose help is also much
more informative. I think more verbose is almost always better.

I can confirm this change causes no regressions on ppc64le Fedora-Rawhide.