On 2007-09-11, Rainer Gerhards <[EMAIL PROTECTED]> wrote: > > But one important thing: I would appreciate if those of you that > experienced the segfaults could try out the new version. I currently > think it will *NOT* fix the problem, but I would like to verify that > (and I have to admit I am not angry if I am wrong...).
Sorry, you were right: *** glibc detected *** rsyslogd: corrupted double-linked list: 0xb7214c98 *** ======= Backtrace: ========= /lib/libc.so.6[0x4152ce3e] /lib/libc.so.6(cfree+0x90)[0x415305d0] rsyslogd(MsgDestruct+0x46)[0x80580b6] rsyslogd[0x804df9a] rsyslogd(llExecFunc+0x3f)[0x805f11f] rsyslogd[0x804d9ea] rsyslogd[0x804db3f] /lib/libpthread.so.0[0x416112db] /lib/libc.so.6(clone+0x5e)[0x4159414e] With 1.19.6. > If it fails, it would be even greater if you could try it in > single-threaded mode: > > ./configure --disable-pthreads Is this safe to use on a busy system? I wouldn't want to start dropping lots of packets.. -jf _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
