Kerberos throwing SIGABORT in exit processing

[John Hascall]

> Ken Raeburn <raeburn at MIT.EDU> writes:
> > I've seen reports of crashes in the thread support before, but aside  
> > from a race condition Ezra reported (is this program multithreaded?),  
> > mostly they seem to do with programs that load multiple versions of  
> > the com_err library and I guess finalization code for one gets run  
> > without it having been properly initialized, or something.  Can you  
> > give me some more details on this case?  For example, what libraries  
> > are getting loaded by this program?

Tom Yu <tlyu at MIT.EDU> writes:
> I wonder if destructors running out of order might do this, e.g.,
> libkrb5support destructor runs before the libcom_err destructor.

Interestingly if I link with -lpthread_dbg instead of -lpthread
I get:

assertion "(&(&_m->os)->n)->initialized == K5_MUTEX_DEBUG_INITIALIZED" \
failed: file "threads.c", line 389, function "krb5int_key_delete"
exited on Abort trap signal; core dumped

John