[29808] in Kerberos
Re: Kerberos throwing SIGABORT in exit processing
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Mon May 12 09:44:21 2008
From: Ken Raeburn <raeburn@MIT.EDU>
To: John Hascall <john@iastate.edu>
In-Reply-To: <32094.1210596238@malison.ait.iastate.edu>
Message-Id: <64748717-CACB-448F-BC58-ACF2146D2286@mit.edu>
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Mon, 12 May 2008 09:43:25 -0400
Cc: kerberos@MIT.EDU
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@MIT.EDU
On May 12, 2008, at 08:43, John Hascall wrote:
> 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
Interesting... does this happen reproducibly?
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 don't recall if gdb on i386-netbsd supports hardware watchpoints,
but if it does, could you trace changes to "key_lock" in util/support/
threads.c and see if it's maybe getting destroyed more than once?
Ken
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
