Kerberos throwing SIGABORT in exit processing

[Tom Yu]

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?

I wonder if destructors running out of order might do this, e.g.,
libkrb5support destructor runs before the libcom_err destructor.