> On Wed, 2013-04-10 at 15:16 +0000, Rainer Gerhards wrote: > > On Wed, 2013-04-10 at 13:10 +0000, Van Der Vliet, Kristian wrote: > > > Thanks Rainer. > > > > > > I've attached the Valgrind log (rsyslog-7.3.10.log) from a version > > > built from Git master as of almost exactly 24 hours ago, and built > > > with the debug symbols intact this time. > > > > > quick update: I had time to try to reproduce in my regular > > environment, unfortunately the bug did not happen there. I now need to > > look at a different setup, seems to be related to the system log > > socket (harder to test these days due to systemd and journal, so I do > > not do this in my regular environment). > > > > Will keep you posted. > > I was lucky, Florian had a usable test environment in place. > Unfortunately, he could also not reproduce. > > So I need your collaboration in order to track this down. I would create a special instrumented version, which you would > need to run on your system and provide me debug logs (best together with valgrind). Would it be OK for you if I just > create a git branch for that and ask you to pull it?
Sure, I can do that. I'll warn you know even I'm beginning to think this is related to me or my build environment and I could be sending you on a wild goose chase, but I am entirely out of ideas on this one. -- Kristian Van Der Vliet
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
