When I initially ran gdb I got the following.... . . Program terminated with signal 11, Segmentation fault. #0 0x0000000000559624 in pam_passwd_conv_proc () Missing separate debuginfos, use: debuginfo-install audit-libs-1.7.13-1.fc11.x86_64 e2fsprogs-libs-1.41.4-12.fc11.x86_64 glibc-2.10.1-5.x86_64 keyutils-libs-1.2-5.fc11.x86_64 krb5-libs-1.6.3-20.fc11.x86_64 libselinux-2.0.80-1.fc11.x86_64 nss-softokn-freebl-3.12.4-3.fc11.x86_64 openssl-0.9.8k-5.fc11.x86_64 pam-1.0.91-6.fc11.x86_64 pam_krb5-2.3.5-1.fc11.x86_64 zlib-1.2.3-22.fc11.x86_64 (gdb) bt #0 0x0000000000559624 in pam_passwd_conv_proc () #1 0x00007f738dfeedd8 in ?? () from /lib64/security/pam_krb5.so . .
I ran debuginfo-install which successfully installed all the related packages, including pam, except for audit-libs due to missing dependency. Probably because of some package I didn't install. For the sake of completeness, I'll install 8.4.1 on another machine which has all the deps met and try to reproduce the problem. -----Original Message----- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Thursday, October 15, 2009 6:07 PM To: Douglas, Ryan Cc: pgsql-bugs@postgreSQL.org Subject: Re: [BUGS] BUG #5121: Segmentation Fault when using pam w/ krb5 "Douglas, Ryan" <rdoug...@arbinet.com> writes: > (gdb) bt > #0 0x0000000000559624 in pam_passwd_conv_proc () > #1 0x00007f738dfeedd8 in _pam_krb5_conv_call (pamh=<value optimized out>, messages=0xb51780, n_prompts=0, responses=0x7fff2e356668) at conv.c:99 > #2 0x00007f738dfefb38 in _pam_krb5_generic_prompter (context=<value optimized out>, data=0x7fff2e357fe0, name=<value optimized out>, banner=<value optimized out>, num_prompts=1, > prompts=<value optimized out>, suppress_password_prompts=1) at prompter.c:330 > #3 0x00007f738dfefe10 in _pam_krb5_normal_prompter (context=0x0, data=0xb51890, name=0x7fff2e356668 "", banner=0x79df27 "", num_prompts=0, prompts=0x101010101010101) > at prompter.c:409 Okay, so the dump is definitely way down inside libpam. The next question is whether it's really libpam's fault, or are we passing it some bad data. Please install the pam-debuginfo RPM that corresponds to the pam version you have, and retry --- hopefully that will add a bit more information to the stack trace. (The debuginfo-install hint you got might help, though I'm not sure why it's referencing audit-libs and not pam ... maybe this code isn't actually in libpam?) regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
