This is the mail archive of the
gcc-bugs@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: 21 Jan 2002 21:51:05 -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: unassigned->ljrittle
Responsible-Changed-By: ljrittle
Responsible-Changed-When: Mon Jan 21 13:51:04 2002
Responsible-Changed-Why:
Mine.
State-Changed-From-To: open->feedback
State-Changed-By: ljrittle
State-Changed-When: Mon Jan 21 13:51:04 2002
State-Changed-Why:
I couldn't reproduce this problem on a sparc-sun-solaris2.7
dual-processor machine against gcc 3.0.4 prerelease.
I saw no boundless memory growth or crashes with
1 or 2 copies of the test program running.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5444