> On Wed, 2013-04-10 at 15:28 +0000, Rainer Gerhards wrote: > > 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: > > 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? > > Well, I created the master-imuxsockbug git branch. It contains some > instrumentation, just to rule out (?) the obvious problem location. > Would appreciate if you could run it. That's probably just the start of > some (many?) iterations...
The valgrind log is attached. Apparently you and I were thinking the same thing! For reference this is how I built: o Pulled that branch. o Copied in the debian/ directory from an existing build: this is originally from the upstream 5.x Ubuntu package, with slight modifications (the version and the configure flags). o Ran autogen.sh o Built with "dpkg-buildpackage -us -uc -tc": this is the equivalent of calling configure with: --enable-mysql --enable-pgsql --enable-mail --enable-imfile --enable-gssapi-krb5 --enable-gnutls --enable-imptcp --enable-valgrind --enable-memcheck --disable-testbench o Copied the resulting .deb to the test machine and ran it under valgrind with the previous rsyslog.conf -- Kristian Van Der Vliet
rsyslog-imuxsockbug.log
Description: Binary data
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.
