From: Guillaume Chazarain <guichaz@yahoo.fr>
To: zsh-workers@sunsite.dk
Subject: Re: deadlock caused by gettext usage in a signal handler
Date: Tue, 4 Dec 2007 19:02:19 +0100 [thread overview]
Message-ID: <20071204190219.037a5400@inria.fr> (raw)
In-Reply-To: <20071203224324.247fb30f.p.w.stephenson@ntlworld.com>
Le Mon, 3 Dec 2007 22:43:24 +0000,
Peter Stephenson <p.w.stephenson@ntlworld.com> a écrit :
> zsh doesn't ever use gettext() directly
I overlooked that, great that Zsh does not use strsignal and perror ;-)
Zsh seems to use dlerror though, hopefully not in a signal handler.
> Alternatively, we could use strerror_r()
strerror_r also calls into gettext, so I don't see how this solves the
problem. I have been caught by the gettext initialization as it's a
bigger malloc consumer than a simple gettext call but according to a
comment by Paul Eggert in:
http://cvs.savannah.gnu.org/viewvc/diffutils/lib/c-stack.c?root=diffutils&view=markup
Do not translate them in the signal handler, since gettext is not
async-signal-safe.
You can see that strerror_r calls gettext in:
http://sourceware.org/cgi-bin/cvsweb.cgi/libc/string/_strerror.c?rev=1.1.2.2&content-type=text/x-cvsweb-markup&cvsroot=glibc
return (char *) _(_sys_errlist_internal[errnum]);
> To get diff output for a test failure while I was writing this I needed
Does that mean you managed to make a reproducible test case?
> to use "diff -a" in ztst.zsh. I'm not sure if the option is universal,
> however.
Confused, I can't see any diff invocation in your patch. From some
googling, POSIX does not specify it
(http://www.opengroup.org/onlinepubs/009695399/utilities/diff.html),
but the BSDs provide it anyway
(http://www.freebsd.org/cgi/man.cgi?query=diff&apropos=0&sektion=0&manpath=FreeBSD+6.0-RELEASE&format=html),
some use GNU diff.
It seems to me a possible solution would be to rewrite strerror() in Zsh
to initially build a static table of translated error messages as
well as the translation of "Unknown error ". Don't know how much this
would delay the Zsh startup though.
Thanks.
--
Guillaume
next prev parent reply other threads:[~2007-12-05 1:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 19:35 Guillaume Chazarain
2007-12-03 22:43 ` Peter Stephenson
2007-12-04 1:39 ` Paul Ackersviller
2007-12-04 18:02 ` Guillaume Chazarain [this message]
2007-12-04 18:24 ` Peter Stephenson
2007-12-04 18:43 ` Guillaume Chazarain
2007-12-04 19:43 ` Peter Stephenson
2007-12-04 19:49 ` Guillaume Chazarain
2007-12-04 20:30 ` Peter Stephenson
2007-12-04 23:09 ` Guillaume Chazarain
2007-12-06 23:02 ` Guillaume Chazarain
2007-12-07 10:35 ` Peter Stephenson
2007-12-07 10:46 ` Guillaume Chazarain
2007-12-07 11:21 ` Bart Schaefer
2007-12-07 11:27 ` Peter Stephenson
2007-12-07 11:57 ` Guillaume Chazarain
2007-12-07 11:29 ` Peter Stephenson
2007-12-10 0:11 Paul Ackersviller
2007-12-10 2:04 ` Bart Schaefer
2007-12-10 3:17 ` Paul Ackersviller
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=20071204190219.037a5400@inria.fr \
--to=guichaz@yahoo.fr \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).