This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/42733] Use of std::string with threads causes process hanging following a fork()
- From: "appfault at hotmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 13 Jan 2010 18:30:08 -0000
- Subject: [Bug libstdc++/42733] Use of std::string with threads causes process hanging following a fork()
- References: <bug-42733-7959@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from appfault at hotmail dot com 2010-01-13 18:30 -------
#0 __gnu_cxx::__exchange_and_add (__mem=0xb3e005a8, __val=-1) at
atomicity.cc:58
#1 0x0804957f in std::string::reserve (this=0xbfffbe20, __res=3017803168) at
basic_string.h:217
#2 0x08049aa2 in std::string::append (this=0xbfffbe20, __s=0x80a3008 "x",
__n=1) at basic_string.tcc:641
#3 0x08049b1b in std::string::operator+= (this=0xbfffbe20, __s=0x1 <Address
0x1 out of bounds>) at char_traits.h:258
#4 0x0804824d in do_stl_stuff ()
#5 0x0804832c in main ()
It never exits from stack frame 0 - gdb says it's alternating between line 58
and 57, but I don't have the source for those. atomicity.cc doesn't appear to
be in the gcc tar - where is it coming from?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42733