On Tue, 2012-03-13 at 21:31 +0100, Peter Czanik wrote:
And another backtrace, this time from openSUSE:
(gdb) backtrace #0 0xb7684e8d in cfg_tree_compile_node () from /lib/libsyslog-ng-3.4.0alpha1.so #1 0xb7684f60 in cfg_tree_compile_node () from /lib/libsyslog-ng-3.4.0alpha1.so #2 0xb7685557 in cfg_tree_compile_rule () from /lib/libsyslog-ng-3.4.0alpha1.so #3 0xb7685954 in cfg_tree_compile () from /lib/libsyslog-ng-3.4.0alpha1.so #4 0xb76859ee in cfg_tree_start () from /lib/libsyslog-ng-3.4.0alpha1.so #5 0xb76808c0 in cfg_init () from /lib/libsyslog-ng-3.4.0alpha1.so #6 0xb76a07ea in main_loop_init () from /lib/libsyslog-ng-3.4.0alpha1.so #7 0x080491a7 in main () (gdb)
Bye,
This one is fixed by this patch, it is triggered by an empty source/destination definition, which seems to be present in the configuration file you use: commit 2d7339985ad8ce9b8d162ca95b3b59d711c27ad2 Author: Balazs Scheidler <bazsi@balabit.hu> Date: Wed Mar 14 09:36:20 2012 +0100 cfg-tree: fixed segfault triggered by empty source/destination object When a source/destination object is empty a segfault happened during the compilation of configuration (for sources) or at the first message (for destinations). This was fixed by handling such cases. Reported-By: Peter Czanik <czp@balabit.hu> Signed-off-by: Balazs Scheidler <bazsi@balabit.hu> -- Bazsi