From: "Stéphane Aulery" <saulery-GANU6spQydw@public.gmane.org>
To: Ma Shimiao
<mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Michael Kerrisk
<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
621057-forwarded-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org
Subject: manpages-dev: please note thread safeness of %m in vfprintf(3)
Date: Sat, 7 Mar 2015 11:38:21 +0100 [thread overview]
Message-ID: <20150307103821.GA2043@free.fr> (raw)
Hello Ma Shimiao,
A Debian user has applied to mention that strerror_r(3) is thread safe.
I quote his message [1]:
> Frome Martin Godisch <martin-AOktpf5JBruELgA04lAiVw@public.gmane.org>, Wed, 6 Apr 2011 09:30:30 +0200
>
> Please add a note to vfprintf(3) telling users that the %m conversion
> specifier is thread safe.
>
> Rationale: errno(3) is thread local, strerror_r(3) is thread safe, and
> vfprintf(3) uses errno and strerror_r (in
> eglibc-2.11.2/stdio-common/vfprintf.c:974).
This is your area, it may interest you.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621057
Regards,
--
Stéphane Aulery
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-03-07 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 10:38 Stéphane Aulery [this message]
[not found] ` <20150307103821.GA2043-GANU6spQydw@public.gmane.org>
2015-03-09 6:20 ` manpages-dev: please note thread safeness of %m in vfprintf(3) Ma Shimiao
[not found] ` <54FD3B97.5050400-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-03-09 7:47 ` Stéphane Aulery
[not found] ` <20150309074735.GA1144-GANU6spQydw@public.gmane.org>
2015-03-09 8:23 ` Ma Shimiao
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=20150307103821.GA2043@free.fr \
--to=saulery-ganu6spqydw@public.gmane.org \
--cc=621057-forwarded-61a8vm9lEZVf4u+23C9RwQ@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mashimiao.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.
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).