I have the same problem, but using cupsys 1.2.2-1.Running /usr/sbin/cupsd -F under gdb shows that the immediate cause of the crash is a SEGV. FWIW, here is the top of the stack trace:
#0 0x08052511 in ?? () #1 0x080ba720 in ?? () #2 0xa7d60c45 in _IO_file_sync () from /lib/tls/i686/cmov/libc.so.6 #3 0x0807dfaf in ?? () #4 0x080ba720 in ?? () #5 0x08097d68 in _IO_stdin_used () #6 0x0000000c in ?? () #7 0x00000003 in ?? () #8 0x0808e491 in _IO_stdin_used () #9 0x08096a70 in _IO_stdin_used () #10 0x0000334a in ?? () #11 0x08096df5 in _IO_stdin_used () #12 0x08097d68 in _IO_stdin_used () #13 0x0809b338 in ConfigurationFile ()
Attached is a gzipped strace of /usr/sbin/cupsd -F crashing. The tail of the that file is as follows:
open("/var/run/cups/cupsd.pid", O_RDWR|O_CREAT|O_LARGEFILE, 0644) = 7
fcntl64(7, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat64(7, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xa7f0d000
_llseek(7, 0, [0], SEEK_CUR) = 0
write(7, "13066\n", 6) = 6
close(7) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
The program crashes so quickly it was practical for me to run it under valgrind. I've also attached the gzipped valgrind output. The tail of that file is as follows:
==13109== Invalid read of size 4 ==13109== at 0x8052511: (within /usr/sbin/cupsd) ==13109== by 0x807DFAE: (within /usr/sbin/cupsd) ==13109== by 0x80667C8: (within /usr/sbin/cupsd) ==13109== by 0x41E1EA7: __libc_start_main (in /lib/tls/i686/cmov/libc-2.3.6.so) ==13109== Address 0x0 is not stack'd, malloc'd or (recently) free'd
Attachment:
cups.log.gz
Description: Unix tar archive
Attachment:
cupsd,valgrind.13109.gz
Description: Unix tar archive