From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19183 invoked by alias); 30 Jan 2012 14:43:16 -0000 Received: (qmail 19174 invoked by uid 22791); 30 Jan 2012 14:43:15 -0000 X-SWARE-Spam-Status: No, hits=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 30 Jan 2012 14:42:53 +0000 From: "howarth at nitro dot med.uc.edu" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2 Date: Mon, 30 Jan 2012 15:36:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: howarth at nitro dot med.uc.edu X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 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: 2012-01/txt/msg03537.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51906 --- Comment #22 from Jack Howarth 2012-01-30 14:42:48 UTC --- (In reply to comment #21) > That gdb session in comment 18 makes no sense, owns_lock can't call trylock. > Your sources don't match your lib. > > I thought this was a problem with WARNING: program timed out. > I didn't notice there were failed assertions too. You'll have to debug it > further yourself. > The simplest one to debug might be 30_threads/recursive_mutex/try_lock/1.cc I'll retry with 30_threads/recursive_mutex/try_lock/1.cc. The program time-out was in the 30_threads/lock/3.cc execution test. The trace I gave you was from the 30_threads/try_lock/3.cc execution test. All remember for exception handling, etc, that darwin uses its own calls in libSystem and not those from libgcc. Only the calls listed in libgcc_ext are used from libgcc these days.