rsyslogd not able to start due to segfault

Issue

• The rsyslog service fails to start

  # systemctl start rsyslog
  Job for rsyslog.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status rsyslog.service" and "journalctl -xe" for details.
  
  # systemctl status rsyslog.service
  ● rsyslog.service - System Logging Service
     Loaded: loaded (/usr/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
     Active: failed (Result: start-limit) since Tue 2018-08-14 15:58:19 +08; 6min ago
       Docs: man:rsyslogd(8)
             http://www.rsyslog.com/doc/
  Main PID: 16651 (code=dumped, signal=SEGV)
  
  Aug 14 15:58:19 example-hostname systemd[1]: Failed to start System Logging Service.
  Aug 14 15:58:19 example-hostname systemd[1]: Unit rsyslog.service entered failed state.
  Aug 14 15:58:19 example-hostname systemd[1]: rsyslog.service failed.
  Aug 14 15:58:19 example-hostname systemd[1]: rsyslog.service holdoff time over, scheduling restart.
  Aug 14 15:58:19 example-hostname systemd[1]: start request repeated too quickly for rsyslog.service
  Aug 14 15:58:19 example-hostname systemd[1]: Failed to start System Logging Service.
  Aug 14 15:58:19 example-hostname systemd[1]: Unit rsyslog.service entered failed state.
  Aug 14 15:58:19 example-hostname systemd[1]: rsyslog.service failed.
  

• The rsyslogd daemon crashes on "Segmentation fault" immediately