tjoen at dds.nl
Sat Feb 25 11:28:42 PST 2017
On Fri, 2017-02-24 at 13:44 -0500, Michael Sweet wrote: > I think if you just run cupsd in gdb you will be able to get a > backtrace when it crashes: > > sudo gdb /usr/sbin/cupsd > run -f > ... wait for crash ... > bt > > and then send the output in a response. (gdb) bt #0 0x00007ffff507c07f in raise () from /lib/libc.so.6 #1 0x00007ffff507d4aa in abort () from /lib/libc.so.6 #2 0x00007ffff37a20a6 in _prelude_thread_deinit () at \ prelude-thread.c:84 #3 0x00007ffff378f3af in prelude_deinit () at prelude.c:268 #4 0x00007ffff744a71f in prelude_send_alert \ (pamh=pamh at entry=0x555555853be0, authval=authval at entry=0) at pam_prelude.c:450 #5 0x00007ffff74451f3 in pam_authenticate (pamh=0x555555853be0, flags=<optimized out>) at pam_auth.c:45 #6 0x0000555555560c99 in cupsdAuthorize (con=0x555555839630) at \ auth.c:616 #7 0x0000555555567fd2 in cupsdReadClient (con=0x555555839630) at \ client.c:857 #8 0x00005555555c4b2a in cupsdDoSelect (timeout=1) at select.c:484 #9 0x00005555555838e8 in main (argc=2, argv=0x7fffffffecf8) at \ main.c:827