http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51906
--- Comment #23 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-01-30 18:04:44 UTC --- The 30_threads/recursive_mutex/try_lock/1.cc execution test on darwin11 built with gcc trunk against Xcode 4.2.1 shows... (gdb) break main Breakpoint 1 at 0x100000dcc: file /sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20120126/libstdc++-v3/testsuite/30_threads/recursive_mutex/try_lock/1.cc, line 37. (gdb) r Starting program: /sw/src/fink.build/gcc47-4.7.0-1/darwin_objdir/x86_64-apple-darwin11.2.0/libstdc++-v3/testsuite/1.exe Reading symbols for shared libraries ++++........................ done Breakpoint 1, main () at /sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20120126/libstdc++-v3/testsuite/30_threads/recursive_mutex/try_lock/1.cc:37 37 mutex_type m; (gdb) s 755 return __gthrw_(pthread_mutex_trylock) (__mutex); (gdb) 37 mutex_type m; (gdb) 755 return __gthrw_(pthread_mutex_trylock) (__mutex); (gdb) 0x0000000100000ea4 in dyld_stub_pthread_mutex_trylock () (gdb) Single stepping until exit from function dyld_stub_pthread_mutex_trylock, which has no line number information. main () at /sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20120126/libstdc++-v3/testsuite/30_threads/recursive_mutex/try_lock/1.cc:39 39 VERIFY( b ); (gdb) 0x0000000100000e8c in dyld_stub___assert_rtn () (gdb) Single stepping until exit from function dyld_stub___assert_rtn, which has no line number information. Assertion failed: (b), function main, file /sw/src/fink.build/gcc47-4.7.0-1/gcc-4.7-20120126/libstdc++-v3/testsuite/30_threads/recursive_mutex/try_lock/1.cc, line 39. Program received signal SIGABRT, Aborted. 0x00007fff927c182a in __kill () (gdb) Single stepping until exit from function __kill, which has no line number information. Program terminated with signal SIGABRT, Aborted. The program no longer exists. Unfortunately Apple doesn't distribute debug versions of libSystem (and I don't know anyone outside of Apple who has managed to build those from the open source darwin releases... although it is theoretically possible). If we need a more detailed debug trace, I'll have to get someone at Apple to do it against one of their libSystem debug builds of Lion.