Bug#511562: rsyslog: segfault on reload when using $AllowedSender

2009-01-15 Thread Juha Koho
On Tue, Jan 13, 2009 at 2:02 AM, Michael Biebl bi...@debian.org wrote: Rainer Gerhards wrote: In my lab, I could reproduce the issue (well, without an abort, unfortunately, but valgrind showed problems). The valgrind run was clean after the change. I would appreciate if you could verify in

Bug#511562: rsyslog: segfault on reload when using $AllowedSender

2009-01-15 Thread Rainer Gerhards
On Thu, 2009-01-15 at 10:03 +0200, Juha Koho wrote: On Tue, Jan 13, 2009 at 2:02 AM, Michael Biebl bi...@debian.org wrote: Rainer Gerhards wrote: In my lab, I could reproduce the issue (well, without an abort, unfortunately, but valgrind showed problems). The valgrind run was clean after

Bug#511562: rsyslog: segfault on reload when using $AllowedSender

2009-01-13 Thread Rainer Gerhards
Hi Michael, Rainer, I'd like (you) to take a look a #509292 first, before making a new release. I am looking at it, but this looks like the dangling issue we have on 4+ core systems from time to time. I am not sure if there will be a quick fix for that. One problem is that I can not reproduce

Bug#511562: rsyslog: segfault on reload when using $AllowedSender

2009-01-12 Thread Rainer Gerhards
Hi all, thanks for the bug report and your help in narrowing it down. I was on vacation and returned today. I have created a patch for this issue (as usual, a dumb mistake...). I'd appreciate if you could give it a try. Available from rsyslog git (debian_lenny branch):

Bug#511562: rsyslog: segfault on reload when using $AllowedSender

2009-01-12 Thread Michael Biebl
Rainer Gerhards wrote: Hi all, thanks for the bug report and your help in narrowing it down. I was on vacation and returned today. I have created a patch for this issue (as usual, a dumb mistake...). I'd appreciate if you could give it a try. Available from rsyslog git (debian_lenny