> > 3049.730531724:966f700: New connect on NSD 0x5d9b4c0. > > ==3607== Thread 3: > > ==3607== Jump to the invalid address stated on the next line > > ==3607== at 0x0: ??? > > ==3607== by 0x6215C3C: MsgSetInputName (in /usr/lib/rsyslog/imuxsock.so) > > ==3607== by 0x6210BD8: ??? (in /usr/lib/rsyslog/imuxsock.so) > > ==3607== by 0x6211392: ??? (in /usr/lib/rsyslog/imuxsock.so) > > ==3607== by 0x43B809: ??? (in /usr/sbin/rsyslogd) > > ==3607== by 0x504A9C9: start_thread (pthread_create.c:300) > > ==3607== by 0x7E6C6FF: ??? > > ==3607== Address 0x0 is not stack'd, malloc'd or (recently) free'd
While this looks pretty obvious, I fail to reproduce the problem in my lab. I have also done some code review and don't see what could triggers this. So I need your help in order to track this down (probably via a couple of iterations). I have created a special instrumented version which permits to keep track how the two pointers that are likely involved evolve over the program's runtime. Please pull this new git branch: http://git.adiscon.com/?p=rsyslog.git;a=shortlog;h=refs/heads/v5-stable-imuxs ock-segfault-instrumented and give it a try. What I am looking at is a) valgrind output b) all lines with "pInputName" from the debug log c) all lines with "msg.c" from the debug log If that would be ok with you, you can also email me the complete log privately. I'll ensure nobody else will see it. Otherwise an excerpt is fine. Note that at this point I am just poking around trying to understand what happens. I probably need some more debug runs to make sense of it. Rainer _______________________________________________ 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
