[29813] in Kerberos
Re: Kerberos throwing SIGABORT in exit processing
daemon@ATHENA.MIT.EDU (John Hascall)
Mon May 12 13:20:18 2008
To: kerberos@MIT.EDU
In-reply-to: Your message of Mon, 12 May 2008 12:07:23 -0400.
<ldv63tjwlok.fsf@cathode-dark-space.mit.edu>
Date: Mon, 12 May 2008 12:18:42 CDT
Message-ID: <289.1210612722@malison.ait.iastate.edu>
From: John Hascall <john@iastate.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@MIT.EDU
> Ken Raeburn <raeburn@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@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
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
