https://bugzilla.balabit.com/show_bug.cgi?id=224 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bazsi@balabit.hu --- Comment #1 from Balazs Scheidler <bazsi@balabit.hu> 2013-02-28 12:20:01 --- hmm... this seems to be a stale memory reference of some kind. the current log msg for which the refcache is being stopped contains an invalid ack_func() function pointer, which then goes boom as we call it. logmsg.c:1495 is the call to the ack_func() pointer. This should not happen (TM). Do you still have the core handy? It'd be nice if you could check the contents of the logmsg structure, like this: gdb <path/to/syslog-ng> <path/to/core> (gdb) frame 1 (gdb) p __tls (gdb) p *__tls.logmsg_current (gdb) x/1024xc __tls.logmsg_current->payload If the pointer to logmsg_current is already pointing to stale data, that would probably mean that a destination driver is unrefing the Log Message more times than it should have. What kind of destinations do you have in this configuration? PS: it might help if you could send me the core file and binaries, so I can work on them. Such issues are quite difficult to track down with a lot of back-and-forth. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.