Dave Wagler wrote:
> On Tue, Aug 6, 2013 at 10:03 PM, Bruce Dubbs <bruce.du...@gmail.com> wrote:
>
>> root [ /usr/src/Linux-PAM-1.1.6 ]# cat > pamtest.c << "EOF"
>>> char pam_start();
>>> int main()
>>> {
>>> return pam_start();
>>> }
>>> EOF
>>> root [ /usr/src/Linux-PAM-1.1.6 ]# gcc -o pamtest pamtest.c -lpam
>>> root [ /usr/src/Linux-PAM-1.1.6 ]# ./pamtest
>>> *Segmentation fault*
>>> root [ /usr/src/Linux-PAM-1.1.6 ]#
>>
>> Do you have:
>>
>> $ ldd ./pamtest
>> linux-vdso.so.1 (0x00007fff007ea000)
>> libpam.so.0 => /lib/libpam.so.0 (0x00007fdf7aa8f000)
>> libc.so.6 => /lib/libc.so.6 (0x00007fdf7a6e2000)
>> libdl.so.2 => /lib/libdl.so.2 (0x00007fdf7a4de000)
>> /lib64/ld-linux-x86-64.so.2 (0x00007fdf7ac9c000)
>>
>> -- Bruce
>>
>
> Close enough:
>
> # ldd ./pamtest
> linux-vdso.so.1 (0x00007fffb79ff000)
> libpam.so.0 => /lib/libpam.so.0 (0x00007febd1551000)
> libc.so.6 => /lib/libc.so.6 (0x00007febd11a3000)
> libdl.so.2 => /lib/libdl.so.2 (0x00007febd0f9f000)
> /lib64/ld-linux-x86-64.so.2 (0x00007febd175e000)
Then I'm out of ideas. There is something wrong with the compilation of
libpam in your system that causes a segfault. When you build pam, did
the tests (make check) pass?
Looking at the code, the small test program actually aborts with the
/var/log/auth.log having the line:
pamtest: PAM pam_start: invalid argument: pamh == NULL
Which is really OK for the test program (configure does not run it, just
tests that it can be linked), but that is not a segfault.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
