bug#33315: gdb set remote exec-file error.

bug#33315: gdb set remote exec-file error.

[Asif]

Summary:
Trying to set a remote executable file name in the gdb *gud* buffer
causes the a single space to be appended to the executable file name.

Steps to reproduce the error:
1) Start emacs.
2) Enable gdmi debug messages in *Messages* buffer.
   M-: (setq gdbmi-debug-mode t)
3) Open the *Messages* buffer and go to *scratch* buffer.
   C-x 2
   C-x b *Messages*
   M-x next-multiframe-window
4) Start gdb which creates the *gud* buffer and makes it the current buffer.
   M-x gdb
   Run gdb (like this): gdb -i=mi
5) Enter the gdb remote exec-file name in the *gud* buffer.
   M-x b *gud*
   set remote exec-file xxx
6) The *Messages* buffer shows the wrong exec-file name value "xxx ",
with the appended space, instead of the correct value "xxx". When this
is sent to the remote gdbserver, the gdbserver report error saying
that remote exec file "xxx " does not exist.
7) *Message* contents shows the following:
   ...
   gdbmi-bnf-incomplete-record-result: param="remote exec-file",value="xxx "
   ...
8) The incorrect exec-file name string is passed to the function named
"gud-filter" located in:
emacs-26.1/lisp/progmodes/gud.el
_
Asif

bug#33315: gdb set remote exec-file error.

[Lars Ingebrigtsen]

Asif <asif.haswarey@gmail.com> writes:

> 7) *Message* contents shows the following:
>    ...
>    gdbmi-bnf-incomplete-record-result: param="remote exec-file",value="xxx "

(This bug report unfortunately got no response at the time.)

When I try this in Emacs 28, I get:

gdbmi-bnf-incomplete-record-result: param="remote exec-file",value="xxx"

So I'm going to go ahead and guess that this has been fixed in the years
since this bug was reported, and I'm closing this bug report.  If the
problem still exists in Emacs 28, please respond to the debbugs address
and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no