As we know it crashed at least once, I'd be more happy with consistent crashing... ;) That inconsistency is part of the problem. It's extremely hard to repro it - I did not even succeed once. I know what this pattern typically means, but so far I've found no more places in code that would "qualify" for this kind of bug... Obviously, either my understanding is wrong or I am still looking at the wrong places. So any further data from the field (crashing or not) is highly appreciated. You are my sole source of troubleshooting information.
Rainer > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:rsyslog- > [EMAIL PROTECTED] On Behalf Of Jan-Frode Myklebust > Sent: Thursday, October 04, 2007 12:10 PM > To: [email protected] > Subject: Re: [rsyslog] rsyslog 1.19.8 released > > On 2007-09-28, Jan-Frode Myklebust <[EMAIL PROTECTED]> wrote: > > On 2007-09-27, Rainer Gerhards <[EMAIL PROTECTED]> wrote: > >> > >> rsyslog 1.19.8 has been released today. Most importantly, it fixes a > bug > > > > Still crashes.. twice today, but I didn't find the trace the > > first time. Here's the trace from the second crash: > > > > FYI: I set the environment variable MALLOC_CHECK_=2 after this > last crash on friday, hoping to get a better trace when it crashed, > but it still haven't crashed.. Not sure if that's good or bad :-) > > > -jf > > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog
