Kerberos throwing SIGABORT in exit processing

[John Hascall]

Has anyone else seen anything like this?
The application completes successfully,
then dies somewhere deep in exit processing
(app's log):

update_server: [info] Closing connection.
Error detected by libpthread: Invalid mutex.
Detected by file "/usr/src/lib/libpthread/pthread_mutex.c", line 334, function "pthread_mutex_unlock".
See pthread(3) for information.
exited on Abort trap signal

And the dump:

(gdb) where
#0  0x4816cfbb in kill () from /usr/lib/libc.so.12
#1  0x4814d6d5 in pthread__errorfunc () from /usr/lib/libpthread.so.0
#2  0x4814a949 in pthread_mutex_unlock () from /usr/lib/libpthread.so.0
#3  0x481196ec in krb5int_key_delete (keynum=K5_KEY_COM_ERR) at threads.c:401
#4  0x48120102 in com_err_terminate () at error_message.c:76
#5  0x4811fdd5 in __dtors () from /usr/athena/lib/libcom_err.so
#6  0x4811fe92 in __do_global_dtors_aux () from /usr/athena/lib/libcom_err.so
#7  0x48122aa5 in fini_fallthru () from /usr/athena/lib/libcom_err.so
#8  0x480566d6 in _rtld_exit () from /usr/libexec/ld.elf_so
#9  0x481c929a in exit () from /usr/lib/libc.so.12
#10 0x08049ace in quit (str=0x8057260 "quit") at update_server.c:205
#11 0x0804999e in main (argc=1, argv=0xbfbff674) at update_server.c:150
#12 0x080494a2 in ___start ()

Using Kerberos5 1.6.3 on
# uname -rms
NetBSD 4.0_BETA2 i386


Thanks,
John