[syslog-ng] syslog-ng crashing at startup

Balazs Scheidler bazsi at balabit.hu
Sat Nov 3 19:21:46 CET 2007

On Thu, 2007-10-25 at 18:09 -0700, Shashank Vinchurkar wrote:
> Hi,
> I have cross compiled syslog-ng-2.0.5 for 64bit mips processor. I am
> using glib-2.12.13. syslog-ng server crashes at startup. Here is the
> stack trace of the crash:

> Core was generated by `./syslog-ng -v -d -F
> -f /syslog-ng/syslog-ng.conf'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x0000005555bd9a30 in free () from /lib64/libc.so.6
> (gdb) bt
> #0  0x0000005555bd9a30 in free () from /lib64/libc.so.6
> #1  0x000000012000e6a8 in log_msg_clear_matches (self=0x120133e10) at
> logmsg.c:512

This is pretty bad. If it crashed in free(), it usually indicates some
kind of heap corruption.

Could you display the contents of *self in frame 1? E.g. something like this:

(gdb) frame 1
(gdb) p *self

The bad news about heap corruptions is that it is very difficult to track 
down without a way to reproduce it locally.


More information about the syslog-ng mailing list