tjoen at dds.nl
Tue Feb 28 11:21:48 PST 2017
On Tue, 2017-02-28 at 17:58 +0100, Helge Blischke wrote: > > Am 28.02.2017 um 12:53 schrieb tjoen <tjoen at dds.nl>: > > > > On Mon, 2017-02-27 at 22:30 +0100, Helge Blischke wrote: > > > > Am 27.02.2017 um 20:13 schrieb tjoen <tjoen at dds.nl>: > > > > With --enable-debug (default is no) in Linux-PAM I get > > > > > > > > #0 0x00007ffff507607f in raise () from /lib/libc.so.6 > > > > #1 0x00007ffff50774aa in abort () from /lib/libc.so.6 > > > > #2 0x00007ffff379c0a6 in _prelude_thread_deinit () at \ > > > > prelude-thread.c:84 > > > > #3 0x00007ffff37893af in prelude_deinit () at prelude.c:268 > > > > #4 0x00007ffff744792f in prelude_send_alert \ > > > > (pamh=pamh at entry=0x55555583c2a0, > > > > authval=authval at entry=0) at pam_prelude.c:450 > > > > #5 0x00007ffff743f88c in pam_authenticate > > > > (pamh=0x555550583c2a0, > > > > flags=<optimized out>) at pam_auth.c:45 > > > > > > > > How do I get rid of that "<optimized out>" ? > > > > > > > > > #6 0x0000555555560c99 in cupsdAuthorize (con=0x555555839630) > > > > > at > > > > > \ > > > > > auth.c:616 > > > First, I’d edit the Makefile (after running configure) and reduce > > > the > > > optimizing number by one > > > (repeat this until the „optimized out“ disappears). OK Cups recompiled with patch replacing PAM_SILENT by 0 and without --enable-debug Linux-PAM recompiled without --enable-debug but CFLAGS LDFLAGS and BUILD_CFLAGS -O0 (-O1 was insufficient) #0 0x00007ffff50b007f in raise () from /lib/libc.so.6 #1 0x00007ffff50b14aa in abort () from /lib/libc.so.6 #2 0x00007ffff37d60a6 in _prelude_thread_deinit () at \ prelude-thread.c:84 #3 0x00007ffff37c33af in prelude_deinit () at prelude.c:268 #4 0x00007ffff744d346 in prelude_send_alert \ (pamh=0x5555557f36f0, authval=0) at pam_prelude.c:450 #5 0x00007ffff74462b0 in pam_authenticate \ (pamh=0x5555557f36f0, flags=0) at pam_auth.c:45 #6 0x00005555555606dd in ?? () #7 0x000055555556429c in ?? () #8 0x0000555555597ee6 in ?? () #9 0x0000555555574745 in ?? () #10 0x00007ffff509d2c1 in __libc_start_main () from /lib/libc.so.6 #11 0x000055555555fb4a in ?? () Bad news is that the patch is not the sollution