On Sun, 11 Apr 2010 22:42:16 -0700, Russ Allbery <r...@debian.org> wrote: > Joel Johnson <mrj...@lixil.net> writes: > >> I have a Sheevaplug (armv5tel) to which I am migrating Kerberos >> services. I've imported an existing database and listing principals >> with kadmin works, ticket issuing works, kpasswd works. However, when >> doing a ticket renewal with `kinit -R` (remotely on or same machine), it >> causes krb5kdc to crash immediately. > > Is this with a TGT that's issued by an earlier version of an MIT Kerberos > server, or one handed out by the current server?
One handed out by the current server, I am running a kdestroy; kinit; kinit -R cycle to test it. For completeness I wait until I have the KDC running under gdb and get the ticket from the same instance. >> Program received signal SIGSEGV, Segmentation fault. >> 0x4023ebac in free () from /lib/libc.so.6 >> (gdb) > > What do you get when you run bt at this prompt? > > Although if it's heap corruption, running krb5kdc under valgrind is > usually the fastest way to identify exactly where the problem is. Yeah, it's getting late - here's the actually useful bt output: (gdb) continue Continuing. Program received signal SIGSEGV, Segmentation fault. 0x4023ebac in free () from /lib/libc.so.6 (gdb) bt #0 0x4023ebac in free () from /lib/libc.so.6 #1 0x400f8cf0 in krb5_free_authdata (context=<value optimized out>, val=0x2f720) at ../../../../src/lib/krb5/krb/kfree.c:144 #2 0x0000e18c in ?? () Cannot access memory at address 0x0 #3 0x0000e18c in ?? () Cannot access memory at address 0x0 Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) Joel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
