[syslog-ng] syslog-ng 3.3.2 seg faulting sending message via tcp
Gergely Nagy
algernon at balabit.hu
Mon Nov 14 07:45:10 CET 2011
"Patrick H." <syslogng at feystorm.net> writes:
> Anyway, gdb backtrace shows:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x40f67940 (LWP 29440)]
> 0x00002b047a812261 in log_pipe_queue (s=0x12d0d94f, msg=0x12d04400,
> path_options=0x40f64150) at logpipe.h:288
> 288 s->queue(s, msg, path_options, s->queue_data);
> (gdb) where
> #0 0x00002b047a812261 in log_pipe_queue (s=0x12d0d94f,
> msg=0x12d04400, path_options=0x40f64150) at logpipe.h:288
Oh dear, oh dear. I know this backtrace. I know it all too well. I'll
see what happened, as this was supposed to be fixed in 3.3.2.
--
|8]
More information about the syslog-ng
mailing list