stdcxx-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Liviu Nicoara (JIRA)" <>
Subject [jira] [Commented] (STDCXX-1071) numpunct facet cache initialization is not thread -safe
Date Wed, 26 Sep 2012 23:57:07 GMT


Liviu Nicoara commented on STDCXX-1071:

The file punct-mt.cpp is a multi-threaded program that tests either the numpunct or the moneypunct
facet accessor interface. If TEST_MONEYPUNCT is defined, the test tests moneypunct. The test
fails with 4.2.x and presumably with all others. The moneypunct version does not fail in my
local runs. I have used SUNPro 5.12 on Linux, but I noticed failures with gcc 4.7.1 as well.
The test case is pointing at the numpunct facet caching code.
> numpunct facet cache initialization is not thread -safe
> -------------------------------------------------------
>                 Key: STDCXX-1071
>                 URL:
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: 22. Localization, Thread Safety
>    Affects Versions: 4.2.1, 4.2.x, 4.3.x, 5.0.0
>         Environment: $ uname -a; CC -V
> Linux behemoth #3 SMP Sat Apr 9 22:49:32 CDT 2011 x86_64 AMD Opteron(tm) Processor
6134 AuthenticAMD GNU/Linux
> CC: Sun C++ 5.12 Linux_i386 2011/11/16
>            Reporter: Liviu Nicoara
>            Priority: Critical
>              Labels: DCII, localization, numpunct, thread-safety
>             Fix For: 4.2.1, 4.2.x, 4.3.x, 5.0.0
>         Attachments: library-reduction.cpp, punct-mt.cpp
>   Original Estimate: 8h
>  Remaining Estimate: 8h
> The bug affects the initialization of the cached data in numpunct facet. The failing
test is 22.locale.numpunct.cpp in certain builds: Linux with SUNPro 5.12, optimized, most
likely to fail. It has been reported (see linked incidents) to fail on SPARC as well. It manifests
in variate ways: sometimes as heap corruption, sometimes as access violations, etc. Test cases
and library reduction programs to follow. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message