From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16264 invoked by alias); 31 Jan 2012 00:01:57 -0000 Received: (qmail 16251 invoked by uid 22791); 31 Jan 2012 00:01:56 -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; Tue, 31 Jan 2012 00:01:43 +0000 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2 Date: Tue, 31 Jan 2012 01:18: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: redi at gcc dot gnu.org 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/msg03607.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51906 --- Comment #24 from Jonathan Wakely 2012-01-31 00:01:41 UTC --- That debug session still doesn't make much sense, are you debugging an optimised executable? I don't need a more detailed trace, just one that actually shows what happens! e.g. knowing what pthread_mutex_trylock returns is necessary, knowing the details of what happens inside that function isn't necessary. What does this return? #include struct mutex { pthread_mutex_t m = PTHREAD_RECURSIVE_MUTEX_INITIALIZER; }; int main() { mutex m; return pthread_mutex_trylock(&m.m); } If the solution is simply to define _XOPEN_SOURCE then that should be done for Lion, but a relevant maintainer for that target should make that decision. libstdc++ relies on POSIX features so if they aren't correctly defined without _XOPEN_SOURCE then that is needed (on GNU/Linux _GNU_SOURCE is always defined)