libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.

libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.

[tot]

>Number:         6015
>Category:       libstdc++
>Synopsis:       3.1 pre libstdc++ number formatting is not mt-safe.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 20 05:16:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     tot@trema.com
>Release:        3.1 20020320 (prerelease)
>Organization:
>Environment:
all
>Description:
libstdc++ was changed 2002-01-22 to use __convert_from_v to format numbers, and __convert_from_v basically does 

setlocale "C"; sprintf; setlocale back

Unfortunately this is completely not thread safe, since all the other threads will change locales too, thus giving completely unpredictable results.  
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

Re: libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.

[paolo]

Synopsis: 3.1 pre libstdc++ number formatting is not mt-safe.

State-Changed-From-To: analyzed->closed
State-Changed-By: paolo
State-Changed-When: Fri Feb  7 15:02:16 2003
State-Changed-Why:
    This is now fixed on glibc2.3.x systems with __uselocale.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6015

Re: libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.

[bkoz]

Synopsis: 3.1 pre libstdc++ number formatting is not mt-safe.

Responsible-Changed-From-To: unassigned->bkoz
Responsible-Changed-By: bkoz
Responsible-Changed-When: Mon Apr  1 11:12:26 2002
Responsible-Changed-Why:
    Mine.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6015

Re: libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.

[bkoz]

Synopsis: 3.1 pre libstdc++ number formatting is not mt-safe.

State-Changed-From-To: suspended->analyzed
State-Changed-By: bkoz
State-Changed-When: Thu Mar 28 14:47:09 2002
State-Changed-Why:
    Note that this is not a new problem. Before this, LANG settings that were not "C" would cause input to fail, unconditionally.
    
    The current code path is not optimal, admittedly. Tricks in the "C" library in the glibc-2.3 timeframe will remove this issue from impacting modern linux systems.
    
    All that is really needed here is some kind of hard-wired "C" locale strtold/sscanf function. Or, some elimination of this step (long threatened by some contributors.)
    
    I believe this defficiency can be improved in the future, without breaking the ABI, so this is really not "critical" to me. Can I downgrade this to serios with low priority?
    
    thanks,
    benjamin
    

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6015

Re: libstdc++/6015: 3.1 pre libstdc++ number formatting is not mt-safe.

[paolo]

Synopsis: 3.1 pre libstdc++ number formatting is not mt-safe.

State-Changed-From-To: open->suspended
State-Changed-By: paolo
State-Changed-When: Sat Mar 23 06:37:45 2002
State-Changed-Why:
    The cleanest way to fix this seems to be that of using a
    sort of thread-safe setlocale which, however, will be
    available only with glibc2.3. For additional details see
    the following thread:
    http://gcc.gnu.org/ml/libstdc++/2002-03/msg00396.html

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6015