From: Stefan Kangas <stefan@marxist.se>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>
Cc: "yates@ieee.org" <yates@ieee.org>,
25488@debbugs.gnu.org,
Randy Yates <randyy@garnerundergroundinc.com>
Subject: bug#25488: 25.1; gdb package interpreter problem
Date: Sun, 15 Sep 2019 03:21:20 +0200 [thread overview]
Message-ID: <CADwFkmmNrdTSjXYw_rWK+CPqg69DOgKwTf+KwHgjJVVXzbv-Fw@mail.gmail.com> (raw)
In-Reply-To: <878tq6oklq.fsf@garnerundergroundinc.com>
Sergio Durigan Junior <sergiodj@sergiodj.net> writes:
> On Friday, January 20 2017, Glenn Morris wrote:
>
>>> 1. configure remote system by running "gdbserver --multi localhost:<port>"
>>>
>>> 2. on host system, run emacs, then "M-x gdb <ret> -i=mi"
>>>
>>> 3. at the gdb prompt:
>>>
>>> file <path-to-exe>
>>> target extended-remote <remote-host-ip-addr>:<port>
>>> set remote exec-file <path-to-exe>
>>> start
>>>
>>> 4.on the remote side, note the message:
>>>
>>> "Cannot exec <path-to-exe> : No such file or directory."
>>>
>>> specifically, note the space between "<path-to-exe>" and ":", which
>>> should not be there. this is the extraneous space.
>>
>>
>> Confirmed on rhel 7.
>>
>> This seems to be due to the " " in:
>>
>> (concat gdb-continuation string " ")
>>
>> in gdb-send, which was added in bug#14847. I've cc'd the author of that change.
>
> Heh, I helped the reporter diagnose this issue, and as it turns out I
> was the culprit!
>
> Thanks for the report, I'll take a look at this later today.
Hi Sergio,
I see that the latest update here was in January 2017. Did you ever get
a chance to look into this issue?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2019-09-15 1:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 20:33 bug#25488: 25.1; gdb package interpreter problem Randy Yates
2017-01-20 19:24 ` Glenn Morris
2017-01-20 19:33 ` Sergio Durigan Junior
2019-09-15 1:21 ` Stefan Kangas [this message]
2019-09-16 13:32 ` Sergio Durigan Junior
2019-09-16 13:44 ` Stefan Kangas
2019-09-23 13:03 ` Noam Postavsky
2019-09-23 13:18 ` Stefan Kangas
2019-09-23 16:19 ` Eli Zaretskii
2019-10-02 13:12 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmmNrdTSjXYw_rWK+CPqg69DOgKwTf+KwHgjJVVXzbv-Fw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=25488@debbugs.gnu.org \
--cc=randyy@garnerundergroundinc.com \
--cc=sergiodj@sergiodj.net \
--cc=yates@ieee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).