This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++/5444: in multi-processor environment basic_string ist not thread safe
- From: ljrittle at gcc dot gnu dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, ljrittle at gcc dot gnu dot org, markus dot breuer at materna dot de, nobody at gcc dot gnu dot org
- Date: 22 Jan 2002 22:13:20 -0000
- Subject: Re: libstdc++/5444: in multi-processor environment basic_string ist not thread safe
- Reply-to: ljrittle at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, ljrittle at gcc dot gnu dot org, markus dot breuer at materna dot de, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: in multi-processor environment basic_string ist not thread safe
Responsible-Changed-From-To: ljrittle->unassigned
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Tue Jan 22 14:13:19 2002
Responsible-Changed-Why:
Doesn't look as related to the part of the code base
I understand as I originally thought.
State-Changed-From-To: feedback->analyzed
State-Changed-By: ljrittle
State-Changed-When: Tue Jan 22 14:13:19 2002
State-Changed-Why:
Agreed, I can reproduce the reduced test case failure
on a two-way MP sparc-sun-solaris2.7 machine using
gcc 3.0.3+"sparc atomicity patch". Parts of
the reduced test case violate libstdc++-v3 threading
rules but I agree that ``std::ostringstream oss''
should be concurrently executable in different threads
and is the root cause of a core dump.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5444