This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2
- From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 30 Jan 2012 14:42:48 +0000
- Subject: [Bug libstdc++/51906] thread lock test failures on darwin11 under Xcode 4.2
- Auto-submitted: auto-generated
- References: <bug-51906-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51906
--- Comment #22 from Jack Howarth <howarth at nitro dot med.uc.edu> 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.