From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: Eli Zaretskii <eliz@gnu.org>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Make sure GDB uses a valid shell when starting the inferior and to perform the "shell" command
Date: Fri, 24 Jul 2015 20:20:00 -0000 [thread overview]
Message-ID: <87a8ul5mud.fsf@redhat.com> (raw)
In-Reply-To: <55B29B84.5000707@ericsson.com> (Simon Marchi's message of "Fri, 24 Jul 2015 16:09:40 -0400")
On Friday, July 24 2015, Simon Marchi wrote:
> On 15-07-24 03:53 PM, Eli Zaretskii wrote:
>> I don't think there are so many shells out there that we run a real
>> risk of forgetting them.
>
> Even though you can try to list all known shells, they won't necessarily
> be in the same location. For example, the servers I work on at work have
> an old version of everything, so I use my own version of bash. SHELL won't
> be /bin/bash but /home/<user>/local/bin/bash. gdb wouldn't recognize it as
> a valid shell.
>
>> And even if we do, there's plenty of time
>> till the next release to hear from those who might be negatively
>> impacted.
>
> I don't think that's true. The number of users who go build and use gdb
> from the master branch is probably negligible. If this affects some users,
> it will most likely be when it gets released in distros (months or years
> after the actual release, depending on the distro).
Yeah, I don't agree with this proposal as well. I will submit a v2
soon, without Eli's proposal, and see what others say. If others also
prefer Eli's idea, we can discuss the details.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-07-24 20:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-24 18:20 Sergio Durigan Junior
2015-07-24 18:34 ` Simon Marchi
2015-07-24 19:10 ` Sergio Durigan Junior
2015-07-24 19:17 ` Eli Zaretskii
2015-07-24 19:29 ` Sergio Durigan Junior
2015-07-24 19:53 ` Eli Zaretskii
2015-07-24 20:09 ` Simon Marchi
2015-07-24 20:20 ` Sergio Durigan Junior [this message]
2015-07-25 7:10 ` Eli Zaretskii
2015-07-25 16:30 ` Sergio Durigan Junior
2015-07-25 16:41 ` Eli Zaretskii
2015-07-25 17:03 ` Sergio Durigan Junior
2015-07-25 17:30 ` Eli Zaretskii
2015-07-25 23:46 ` Sergio Durigan Junior
2015-07-24 20:29 ` Paul_Koning
2015-07-24 20:38 ` Simon Marchi
2015-07-24 20:51 ` Paul_Koning
2015-07-24 21:36 ` Matt Rice
2015-07-25 7:20 ` Eli Zaretskii
[not found] ` <87y4i547lk.fsf@redhat.com>
2015-07-25 7:16 ` Eli Zaretskii
2015-07-24 20:18 ` Andreas Schwab
2015-07-25 7:11 ` Eli Zaretskii
2015-07-25 7:54 ` Andreas Schwab
2015-07-25 8:09 ` Eli Zaretskii
2015-07-24 19:54 ` Simon Marchi
2015-07-24 18:43 ` Luis Machado
2015-07-24 19:08 ` Sergio Durigan Junior
2015-07-24 19:15 ` Eli Zaretskii
2015-07-24 20:38 ` [PATCH v2] " Sergio Durigan Junior
2015-07-26 0:14 ` [PATCH v3] " Sergio Durigan Junior
2015-07-26 8:05 ` Doug Evans
2015-07-26 17:03 ` Doug Evans
2015-07-26 19:26 ` Sergio Durigan Junior
2015-07-26 20:48 ` Doug Evans
2015-07-28 23:11 ` Pedro Alves
2015-07-29 19:21 ` Sergio Durigan Junior
2015-07-26 15:04 ` Eli Zaretskii
2015-07-28 19:58 ` [PATCH] Warn the user when $SHELL is invalid Sergio Durigan Junior
2015-07-28 23:12 ` Pedro Alves
2015-07-29 19:22 ` Sergio Durigan Junior
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=87a8ul5mud.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox