Assertion failed for krb5kdc

Ken Raeburn raeburn at MIT.EDU
Mon Oct 19 14:29:03 EDT 2009


On Oct 16, 2009, at 19:19, eightball wrote:
> I am not familiar with gdb. If I did it incorrectly, some help would
> be appreciated:

No, it looks right...

> (gdb) run -n
> Starting program: /local/BuildArea/krb5/krb5-1.7/src/kdc/krb5kdc -n
>
> Breakpoint 1, main (argc=2, argv=0xffbef934) at main.c:838
> 838         if (strrchr(argv[0], '/'))
> (gdb) break krb5int_pthread_loaded
> Breakpoint 2 at 0xff182024: file threads.c, line 135.
> (gdb) break loaded_test_aux
> Breakpoint 3 at 0xff181fe0: file threads.c, line 126.
> (gdb) continue
> Continuing.
> Assertion failed: k5int_i->did_run != 0, file krb5_libinit.c, line 63

Okay, it looks like it's never even calling krb5int_pthread_loaded,  
which should mean that it's always following the code path (in  
selecting macro definitions) that assumes the thread support is always  
linked in.  This would be dependent on some configuration macros,  
HAVE_PRAGMA_WEAK_REF and NO_WEAK_PTHREADS; can you see which are set  
in include/autoconf.h in the build tree?  The former should be defined  
(based on tests of the compiler, so it may also depend on which  
compiler you're using), and the latter should not (selected in the  
configure script based on the OS version).

Ken



More information about the Kerberos mailing list