From: Noam Postavsky <npostavs@gmail.com>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>
Cc: "yates@ieee.org" <yates@ieee.org>,
25488@debbugs.gnu.org,
Randy Yates <randyy@garnerundergroundinc.com>,
Stefan Kangas <stefan@marxist.se>
Subject: bug#25488: 25.1; gdb package interpreter problem
Date: Mon, 23 Sep 2019 09:03:24 -0400 [thread overview]
Message-ID: <87sgon88rn.fsf@gmail.com> (raw)
In-Reply-To: <87impsnz84.fsf@paluero> (Sergio Durigan Junior's message of "Mon, 16 Sep 2019 09:32:27 -0400")
> Sergio Durigan Junior <sergiodj@sergiodj.net> writes:
>
>> Yeah, I had the chance to look into it, and even though I don't remember
>> the details now, I have a patch here that seems to work for me. I'm
>> attaching it to this message; can you check if it fixes the problem for
>> you, please?
>>
>> It seems strange that the extra whitespace was added by mistake there.
>> I'm a bit afraid that there is a case which I haven't envisioned and
>> which requires that whitespace, but I couldn't come up with a testing
>> scenario that triggers the error. I tested this by debugging a binary
>> with and without arguments (i.e., "/bin/true" and "/bin/true --help"),
>> and both worked fine.
> Thanks for reporting back and providing a patch. Could someone more
> familiar with this code please help test and review this?
I'm not very familiar with the code, but looking around, it seems quite
likely that the extra " " was just due to a copy paste error.
next prev parent reply other threads:[~2019-09-23 13:03 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
2019-09-16 13:32 ` Sergio Durigan Junior
2019-09-16 13:44 ` Stefan Kangas
2019-09-23 13:03 ` Noam Postavsky [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sgon88rn.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=25488@debbugs.gnu.org \
--cc=randyy@garnerundergroundinc.com \
--cc=sergiodj@sergiodj.net \
--cc=stefan@marxist.se \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.