public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "appfault at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/42733] Use of std::string with threads causes process hanging following a fork()
Date: Wed, 13 Jan 2010 18:30:00 -0000	[thread overview]
Message-ID: <20100113183008.622.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42733-7959@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2010-01-13 18:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-13 17:54 [Bug libstdc++/42733] New: " appfault at hotmail dot com
2010-01-13 17:57 ` [Bug libstdc++/42733] " appfault at hotmail dot com
2010-01-13 18:24 ` jwakely dot gcc at gmail dot com
2010-01-13 18:30 ` appfault at hotmail dot com [this message]
2010-01-13 18:49 ` paolo dot carlini at oracle dot com
2010-01-13 18:50 ` appfault at hotmail dot com
2010-01-13 18:53 ` appfault at hotmail dot com
2010-01-13 18:57 ` paolo dot carlini at oracle dot com
2010-01-13 20:07 ` appfault at hotmail dot com
2010-01-13 20:34 ` paolo dot carlini at oracle dot com
2010-01-13 21:09 ` appfault at hotmail dot com
2010-01-13 21:42 ` paolo dot carlini at oracle dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100113183008.622.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).