Strange segmentation fault in libkrb5.so.3.3 (1.6.4-beta1)

[Russ Allbery]

Dan Searle <dan.searle at censornet.com> writes:

> Ok, authenticating a user against a Windows 2008R2 KDC with an expired
> passwords is a 100% sure way of recreating this error. I've recreated
> the error using an Ubuntu source package to compile version
> krb5-1.6.dfsg.3~beta1 from sources with debug symbols, and here's the
> gdb stack trace I get:

> #0  0xb7f9838b in ?? () from /lib/ld-linux.so.2
> #1  0xb7f9dc80 in ?? () from /lib/ld-linux.so.2
> #2  0xb70c087d in krb5_get_error_message (ctx=0x8220428, 
> code=-1765328324) at ../../../../src/lib/krb5/krb/kerrs.c:87
> #3  0x7de66ec4 in ?? () from /lib/security/pam_krb5.so
> #4  0x7de6745f in ?? () from /lib/security/pam_krb5.so
> #5  0x7de6623a in ?? () from /lib/security/pam_krb5.so
> #6  0x7de640be in pam_sm_authenticate () from /lib/security/pam_krb5.so
> #7  0xb7df51c8 in ?? () from /lib/libpam.so.0
> #8  0xb7df4a8d in pam_authenticate () from /lib/libpam.so.0
> [snip]

> kerrs.c:87 corresponds to the following call:

>     return krb5int_get_error (&ctx->err, code);

> krb5int_get_error is an exported symbol in the libkrb5support library, 
> so what's going on with ld? Is it failing to find the symbol?

Could you build libpam-krb5 with debugging symbols as well?  It would be
useful to see where that call to krb5_get_error_message is coming from.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>