From: Sergio Durigan Junior via Gdb-patches <gdb-patches@sourceware.org>
To: Tom Tromey <tom@tromey.com>
Cc: Sergio Durigan Junior via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [PR gdb/28369] Use get_shell on gdb/ser-pipe.c
Date: Thu, 30 Sep 2021 18:20:11 -0400 [thread overview]
Message-ID: <87zgrtbt9g.fsf@paluero> (raw)
In-Reply-To: <87h7e20xni.fsf@tromey.com> (Tom Tromey's message of "Thu, 30 Sep 2021 11:40:49 -0600")
On Thursday, September 30 2021, Tom Tromey wrote:
>>>>>> "Sergio" == Sergio Durigan Junior via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Sergio> PR gdb/28369 reports that gdb/ser-pipe.c has an 'execl' function call
> Sergio> with a hard-coded "/bin/sh" as its argument. We've had 'get_shell'
> Sergio> for a while now, which is conscious about the SHELL environment and a
> Sergio> better alternative to always calling "/bin/sh".
>
> Thanks, this is ok.
Thanks, Tom.
Pushed: 906e2b7664c5becfa3e10717a7d530e87fdab4ec
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
prev parent reply other threads:[~2021-09-30 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 21:34 Sergio Durigan Junior via Gdb-patches
2021-09-30 17:40 ` Tom Tromey
2021-09-30 22:20 ` Sergio Durigan Junior via Gdb-patches [this message]
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=87zgrtbt9g.fsf@paluero \
--to=gdb-patches@sourceware.org \
--cc=sergiodj@sergiodj.net \
--cc=tom@tromey.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