Bug 13346 - 4: syslog-ng -s Segmentation fault
Summary: 4: syslog-ng -s Segmentation fault
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Guillaume Rousse
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-05-08 13:04 CEST by Bit Twister
Modified: 2015-07-01 11:05 CEST (History)
0 users

See Also:
Source RPM: syslog-ng-3.4.5-1.mga4.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2014-05-08 13:04:10 CEST 
Description of problem:

# syslog-ng -s
Segmentation fault

Problem is syslog-ng should at least give file being processed and line causing the fault.


Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. cat > /etc/syslog-ng/conf.d/my_syslog-ng.conf<EOD
@version:3.4
@include "scl.conf"
EOD

2. syslog-ng -s

Workaround:
Do not put "  @include "scl.conf"  " in user created conf file.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-05-08 18:49:28 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => guillomovitch

Comment 1 Guillaume Rousse 2014-06-01 14:51:13 CEST 
Much simpler to reproduce: just add a second "@include "scl.conf" statement in main configuration file. However, this is an upstream issue, not much we can do here...

Status: NEW => ASSIGNED

Comment 2 Bit Twister 2015-07-01 11:05:11 CEST 
(In reply to Guillaume Rousse from comment #1)
> Much simpler to reproduce: just add a second "@include "scl.conf" statement
> in main configuration file. However, this is an upstream issue, not much we
> can do here...

Ok, since I am no longer using syslog-ng I'll mark this resolved wontfix

Status: ASSIGNED => RESOLVED
Resolution: (none) => WONTFIX
Note You need to log in before you can comment on or make changes to this bug.