This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Bug libstdc++/32261] Thread race segfault in std::string::append with -O and -s

From: "Andrew Pinski" <pinskia at gmail dot com>
To: gcc-bugzilla at gcc dot gnu dot org
Cc: gcc-bugs at gcc dot gnu dot org
Date: Wed, 13 Jun 2007 19:56:27 -0700
Subject: Re: [Bug libstdc++/32261] Thread race segfault in std::string::append with -O and -s
References: <bug-32261-7959@http.gcc.gnu.org/bugzilla/> <20070614024232.9170.qmail@sourceware.org>

bug 21334 seems to deal with multiple threads accessing the same shared object
at the same time.  However, the sample code provided here involves separate
private objects so there should not be any such issues.  If it is not possible
to assume that separate threads can access unrelated STL objects at the same
time, then this would imply that all STL operations (regardless of the object)
must be serialized!

The empty string is the same object really.

-- Pinski

References:
- [Bug c++/32261] New: Thread race segfault in std::string::append with -O and -s
  - From: appfault at hotmail dot com
- [Bug libstdc++/32261] Thread race segfault in std::string::append with -O and -s
  - From: jlawson-gcc at bovine dot net

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]