On Thu, 2009-01-15 at 18:58 +0100, Lorenzo M. Catucci wrote: > I've just tried again rsyslog on my 8 core mail server, and got the very > same crash from september/october.
So, without valgrind, can you reproduce the issue each time you start it? That would be very useful. > I've restarted the server under > valgrind control, and all seems to be running well... I guess the issue here is that valgrind slows down things and also simulates (I think) 2 CPUs only. > A good 2009 to all! same to you! Thanks for being persistent with this issue (it begins to drive me crazy). >From what I have learned so far we seem to have a race condition that causes memory corrupt. The backtrace you include also points into that direction. Those few cases where I got a usable backtrace all point to the very same location. However, that does not mean this location has the bug. It seems to occur some time earlier, and manifests when the message is destructed. It could be a double-free or even some wild memory access that accidently overwrites some structures. If we are able to get a stable repro, and we are able to run with at least some minimal diagnostics, we may be much better of tackeling that beast. First step is to see that we get a stable repro. If we do, I need to think about minimal debug. The full debugging system makes the bug disappear, I think because it changes the timing. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
