From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20444 invoked by alias); 13 Jan 2010 21:09:48 -0000 Received: (qmail 20377 invoked by uid 48); 13 Jan 2010 21:09:35 -0000 Date: Wed, 13 Jan 2010 21:09:00 -0000 Message-ID: <20100113210935.20376.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libstdc++/42733] Use of std::string with threads causes process hanging following a fork() In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "appfault at hotmail dot com" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-01/txt/msg01572.txt.bz2 ------- Comment #10 from appfault at hotmail dot com 2010-01-13 21:09 ------- I didn't mean a test that the pthread_atfork() call works at the pthread layer, but that GCC's use of pthread_atfork() etc was appropriate, given GCC's use of pthread_mutex. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42733