Hi Michael, The function "localeconv" returns a pointer to a structure which might be overwritten by subsequent calls to `localeconv' or by calls to `setlocale', so it is not thread-safe. Signed-off-by: Peng Haitao <penght@xxxxxxxxxxxxxx> --- man3/localeconv.3 | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/man3/localeconv.3 b/man3/localeconv.3 index 7b6a1da..86b2624 100644 --- a/man3/localeconv.3 +++ b/man3/localeconv.3 @@ -21,7 +21,7 @@ .\" the source, must acknowledge the copyright and authors of this work. .\" License. .\" Modified Sat Jul 24 19:01:20 1993 by Rik Faith (faith@xxxxxxxxxx) -.TH LOCALECONV 3 1993-04-25 "GNU" "Linux Programmer's Manual" +.TH LOCALECONV 3 2010-12-23 "GNU" "Linux Programmer's Manual" .SH NAME localeconv \- get numeric formatting information .SH SYNOPSIS @@ -47,6 +47,13 @@ Programs may also use the functions and .BR strfmon (3), which behave according to the actual locale in use. +.SH ATTRIBUTES +.SS Multithreading (see pthreads(7)) +The +.BR localeconv () +function is not thread-safe, since it returns a pointer to a structure which +might be overwritten by subsequent calls to `localeconv' or by calls to +`setlocale'. .SH "CONFORMING TO" C89, C99. .SH BUGS -- 1.7.0.1 -- Best Regards, Peng Haitao -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html