cups crashes when log options is empty

[psklenar]

1, have a wrongly written directive for new way for logging:
#AccessLog syslog
AccessLog
^ no file after this option
2, cups cannot start, coredump

Process Core Dump (PID 21244/UID 0).
START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@3-21244-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
ervice: Main process exited, code=dumped, status=11/SEGV
ervice: Failed with result 'core-dump'.
STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=cups comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
1245]: Process 21236 (cupsd) of user 0 dumped core.

   Stack trace of thread 21236:
   #0  0x000055bd6bbdd8ce cupsdLogRequest (cupsd)
   #1  0x000055bd6bbbf9a1 cupsdWriteClient (cupsd)
   #2  0x000055bd6bbe9c3b cupsdDoSelect (cupsd)
   #3  0x000055bd6bbb724b main (cupsd)
   #4  0x00007ff10863ef6a __libc_start_main (libc.so.6)
   #5  0x000055bd6bbb857a _start (cupsd)

---

it could say its wrongly used or something

[michaelrsweet]

Confirmed.

[michaelrsweet]

[master 9dcb503] Fix crash when AccessLog is NULL (Issue #5309)

[branch-2.2 dfe5192] Fix crash when AccessLog is NULL (Issue #5309)