We should check NetBSD results more often; they're currently reporting assertion failures in the thread library for a lot of our test programs, though the core files I've looked at so far aren't giving me terribly useful stack traces. Here's one example from a program run under gdb with no particular environment setup: (gdb) run ATHENA.MIT.EDU Starting program: /usr/home/krbsnap/autobuild-shared/ work-20080814.0500/krb5-current/src/lib/krb5/os/t_locate_kdc ATHENA.MIT.EDU t_locate_kdc: Error detected by libpthread: Destroying locked mutex. Detected by file "/home/builds/ab/netbsd-3-0-RELEASE/src/lib/ libpthread/pthread_mutex.c", line 135, function "pthread_mutex_destroy". See pthread(3) for information. Program received signal SIGABRT, Aborted. [Switching to LWP 1] 0x000000016022d860 in kill () from /usr/lib/libc.so.12 (gdb) bt #0 0x000000016022d860 in kill () from /usr/lib/libc.so.12 #1 0x00000001601e4968 in pthread__errorfunc () from /usr/lib/ libpthread.so.0 #2 0x00000001601dfd38 in pthread_mutex_destroy () from /usr/lib/libpthread.so.0 #3 0x00000001600f3ebc in profile_free_file_data (data=0x120020200) at prof_file.c:602 #4 0x00000001600f334c in profile_dereference_data (data=0x120020200) at prof_file.c:547 #5 0x00000001600f3be4 in profile_free_file (prf=0x12001c0e0) at prof_file.c:570 #6 0x00000001600f4328 in profile_close_file (prf=0x12001c0e0) at prof_file.c:613 #7 0x00000001600eff54 in profile_open_file (filespec=0x120020200 "", ret_prof=0x1ffffea00) at prof_file.c:297 #8 0x00000001600f8c0c in profile_init (files=0x0, ret_profile=0x12001a048) at prof_init.c:43 #9 0x00000001600e5164 in os_init_paths (ctx=0x12001a000, kdc=0) at init_os_ctx.c:343 #10 0x00000001600e5214 in krb5_os_init_context (ctx=0x12001a000, kdc=6) at init_os_ctx.c:397