On 04/25/13 05:49, Peng Haitao wrote:
Before glibc 2.16, fmtmsg() is not thread-safe.
Since glibc 2.16, it is thread-safe, the patch can refer to URL:
http://sourceware.org/git/?p=glibc.git;a=commit;h=7724defcf8873116fe4efab256596861eef21a94
Applied to my local branch for this work.
Thank you, Peng.
Cheers,
Michael
quoted hunk
Signed-off-by: Peng Haitao <redacted>
---
man3/fmtmsg.3 | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/man3/fmtmsg.3 b/man3/fmtmsg.3
index f4b3d6f..3e3d3f9 100644
--- a/man3/fmtmsg.3
+++ b/man3/fmtmsg.3
@@ -222,6 +222,16 @@ is the string printed when a message of this class is processed by
.SH VERSIONS
.BR fmtmsg ()
is provided in glibc since version 2.1.
+.SH ATTRIBUTES
+.SS Multithreading (see pthreads(7))
+Before glibc 2.16, the
+.BR fmtmsg ()
+uses a static variable that is not protected, so it is not thread-safe.
+
+Since glibc 2.16, the
+.BR fmtmsg ()
+uses a lock to protect static variable, so it is thread-safe.
+.\" Modified in commit 7724defcf8873116fe4efab256596861eef21a94
.SH CONFORMING TO
The functions
.BR fmtmsg ()
--
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