From: Phillip Wood <phillip.wood123@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>, phillip.wood@dunelm.org.uk
Cc: Git Mailing List <git@vger.kernel.org>,
carenas@gmail.com,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 4/4] terminal: restore settings on SIGTSTP
Date: Tue, 8 Mar 2022 10:54:59 +0000 [thread overview]
Message-ID: <09a0bb3f-1e03-5692-f54e-2ff080c21cc8@gmail.com> (raw)
In-Reply-To: <220307.86o82hzucl.gmgdl@evledraar.gmail.com>
On 07/03/2022 14:45, Ævar Arnfjörð Bjarmason wrote:
>[...]
> On Mon, Mar 07 2022, Phillip Wood wrote:
>
>> On 07/03/2022 11:49, Ævar Arnfjörð Bjarmason wrote:
>>> On Mon, Mar 07 2022, Phillip Wood wrote:
>>>
>>>> Hi Ævar
>>>>
>>>> On 05/03/2022 13:59, Ævar Arnfjörð Bjarmason wrote:
>>>>> [...]
>>>>>> int save_term(unsigned flags)
>>>>>> {
>>>>>> + struct sigaction sa;
>>>>>> +
>>>>>> if (term_fd < 0)
>>>>>> term_fd = (flags & SAVE_TERM_STDIN) ? 0
>>>>>> : open("/dev/tty", O_RDWR);
>>>>>> @@ -44,6 +136,26 @@ int save_term(unsigned flags)
>>>>>> if (tcgetattr(term_fd, &old_term) < 0)
>>>>>> return -1;
>>>>>> sigchain_push_common(restore_term_on_signal);
>>>>>> + /*
>>>>>> + * If job control is disabled then the shell will have set the
>>>>>> + * disposition of SIGTSTP to SIG_IGN.
>>>>>> + */
>>>>>> + sigaction(SIGTSTP, NULL, &sa);
>>>>>> + if (sa.sa_handler == SIG_IGN)
>>>>>> + return 0;
>>>>>> +
>>>>>> + /* avoid calling gettext() from signal handler */
>>>>>> + background_resume_msg = xstrdup(_("error: cannot resume in the background"));
>>>>>> + restore_error_msg = xstrdup(_("error: cannot restore terminal settings"));
>>>>> You don't need to xstrdup() the return values of gettext() (here
>>>>> _()),
>>>>> you'll get a pointer to static storage that's safe to hold on to for the
>>>>> duration of the program.
>>>>
>>>> I had a look at the documentation and could not see anything about the
>>>> lifetime of the returned string, all it says is "don't alter it"
>>> I think this is overed in "11.2.7 Optimization of the *gettext
>>> functions", a pedantic reading might suggest not, but what's meant with
>>> the combination of that API documentation & the description of how MO
>>> files work is that you're just getting pointers into the already-loaded
>>> translation catalog, so it's safe to hold onto the pointer and re-use it
>>> later.
>>
>> Strictly that section only shows it is safe if there are no other
>> calls to gettext() before the returned string is used. I agree the
>> implementation is likely to be just returning static strings but I
>> can't find anywhere that says another implementation (e.g. on
>> macos/*bsd) has to do that.
>
> I agree. I'm 99.99% sure this is safe & portable use of the API, but I'm
> having some trouble finding documentation for that...
>
>>> In any case, if we're going to be paranoid about gettext() it would make
>>> sense to propose that as some general change to how we use it, we rely
>>> on this assumption holding in a lot of our use of the API:
>>> git grep '= _\('
>>> Rather than sneak that partcular new assumption in here in this
>>> already
>>> tricky code...
>>
>> The ones I looked at are mostly not calling gettext() again before
>> using the translated string (there is one exception in
>> builtin/remote.c).
>
> Doesn't validate_encoding() in convert.c, process_entry() in
> merge-ort.c, setup_unpack_trees_porcelain() in unpack-trees.c cmd_mv()
> in builtin/mv.c etc. qualify?
I only checked a few, cmd_mv() always assigns to the same variable so
the previous value is overwritten anyway, some of the others such as
unpack_trees are assuming the return value is valid after a subsequent
call to gettext(). I found[1] which states
The string returned must not be modified by the program and can
be invalidated by a subsequent call to bind_textdomain_codeset()
or setlocale(3C).
so I think we can drop the copying.
> I.e. for a hypothetical gettext() that always returned the same pointer
> and just overwrote it with the latest message those would all emit bad
> output, wouldn't they?
>
>> In restore_term() I'm checking if the messages are NULL to see if job
>> control is enabled, I could use a flag but I'm inclined to just keep
>> coping the strings.
>
> Checking if they're NULL is orthagonal to whether we xstrdup()
> them. I.e. you'd just skip the xstrdup() and replace the FREE_AND_NULL
> with a "= NULL" assignment, no?
Yes, I'm not sure what I was thinking when I wrote that.
Best Wishes
Phillip
[1]
https://docs.oracle.com/cd/E88353_01/html/E37843/gettext-3c.html#REFMAN3Agettext-3c
next prev parent reply other threads:[~2022-03-08 10:55 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 13:11 [PATCH 0/4] builtin add -p: hopefully final readkey fixes Phillip Wood
2022-03-04 13:11 ` [PATCH 1/4] terminal: use flags for save_term() Phillip Wood
2022-03-04 20:40 ` Ramsay Jones
2022-03-07 11:11 ` Phillip Wood
2022-03-07 20:21 ` Ramsay Jones
2022-03-08 10:41 ` Phillip Wood
2022-03-05 14:02 ` Ævar Arnfjörð Bjarmason
2022-03-07 10:45 ` Phillip Wood
2022-03-07 12:06 ` Ævar Arnfjörð Bjarmason
2022-03-04 13:11 ` [PATCH 2/4] terminal: don't assume stdin is /dev/tty Phillip Wood
2022-03-04 20:42 ` Ramsay Jones
2022-03-04 13:11 ` [PATCH 3/4] terminal: work around macos poll() bug Phillip Wood
2022-03-04 13:11 ` [PATCH 4/4] terminal: restore settings on SIGTSTP Phillip Wood
2022-03-05 13:59 ` Ævar Arnfjörð Bjarmason
2022-03-07 10:53 ` Phillip Wood
2022-03-07 11:49 ` Ævar Arnfjörð Bjarmason
2022-03-07 13:49 ` Phillip Wood
2022-03-07 14:45 ` Ævar Arnfjörð Bjarmason
2022-03-08 10:54 ` Phillip Wood [this message]
2022-03-09 12:19 ` Johannes Schindelin
2022-03-10 16:06 ` Phillip Wood
2022-03-09 11:03 ` [PATCH v2 0/4] builtin add -p: hopefully final readkey fixes Phillip Wood
2022-03-09 11:03 ` [PATCH v2 1/4] terminal: use flags for save_term() Phillip Wood
2022-03-11 16:52 ` Carlo Arenas
2022-03-14 10:49 ` Phillip Wood
2022-03-09 11:03 ` [PATCH v2 2/4] terminal: don't assume stdin is /dev/tty Phillip Wood
2022-03-09 11:03 ` [PATCH v2 3/4] terminal: work around macos poll() bug Phillip Wood
2022-03-10 13:35 ` Ævar Arnfjörð Bjarmason
2022-03-10 16:02 ` Phillip Wood
2022-03-10 18:02 ` Junio C Hamano
2022-03-09 11:03 ` [PATCH v2 4/4] terminal: restore settings on SIGTSTP Phillip Wood
2022-03-09 23:10 ` [PATCH v2 0/4] builtin add -p: hopefully final readkey fixes Junio C Hamano
2022-03-09 23:37 ` Junio C Hamano
2022-03-10 13:28 ` Phillip Wood
2022-03-10 18:18 ` Phillip Wood
2022-03-10 18:53 ` Junio C Hamano
2022-03-10 13:25 ` Johannes Schindelin
2022-03-10 16:08 ` Phillip Wood
2022-03-15 10:57 ` [PATCH v3 " Phillip Wood
2022-03-15 10:57 ` [PATCH v3 1/4] terminal: use flags for save_term() Phillip Wood
2022-03-15 10:57 ` [PATCH v3 2/4] terminal: don't assume stdin is /dev/tty Phillip Wood
2022-03-15 17:42 ` Junio C Hamano
2022-03-15 18:01 ` rsbecker
2022-03-15 19:05 ` Junio C Hamano
2022-03-15 19:38 ` rsbecker
2022-03-15 10:57 ` [PATCH v3 3/4] terminal: work around macos poll() bug Phillip Wood
2022-03-15 10:57 ` [PATCH v3 4/4] terminal: restore settings on SIGTSTP Phillip Wood
2022-03-15 17:51 ` Junio C Hamano
2022-03-16 18:54 ` [PATCH v4 0/4] builtin add -p: hopefully final readkey fixes Phillip Wood
2022-03-16 18:54 ` [PATCH v4 1/4] terminal: use flags for save_term() Phillip Wood
2022-03-16 18:54 ` [PATCH v4 2/4] terminal: don't assume stdin is /dev/tty Phillip Wood
2022-03-16 18:54 ` [PATCH v4 3/4] terminal: work around macos poll() bug Phillip Wood
2022-03-16 18:54 ` [PATCH v4 4/4] terminal: restore settings on SIGTSTP Phillip Wood
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=09a0bb3f-1e03-5692-f54e-2ff080c21cc8@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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://80x24.org/mirrors/git.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).