>>>Mhh... this looks really strange. I'll dig into it later today, but >>>the problem may actually be related to your system. >>> >>>Could you try to install from source on a new system (VM) and see if >>>the same problem exists (I mean without creating deb packages and so...). >> >>Yeah, I'll set some test systems in various states and see if I can >>reproduce or narrow it down. > >O.K I think we can put this one down to a fubar'd build environment; on a new machine I can build a working version of 7.3.10, both with and without my >AMQP patches, that doesn't exhibit this problem. > >Sorry for the wild goose chase.
I take it back: I can still crash it, but it's just far harder. Just for good measure I can crash the 7.3.10 AMD64 version from the adiscon apt repository, too. If I use something like: while ((1));do logger "message $RANDOM";done I.e. send messages via. 'logger' in a tight loop, it's just fine. However if I try my logsmash tool (https://github.com/Vanders/logsmash) I can crash imuxsock within a few messages (logsmash -c -l 10), every time. Just for good measure I tried logsmash against rsyslog 5.8.6 and it doesn't crash, so this really could be a new bug in 7.x somewhere. Can you see if you can reproduce what I'm seeing with logsmash? If not then I'll shut up about it and put it down to gremlins, but it might be worth checking quickly? -- 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.
