The foreach assuming json_object shouldn't be a problem, because it checks for the same before invoking the loop. All I can commit to is I can re-look at it once I have some time at hand.
Which version of json-c are you using? On Fri, Jun 12, 2015 at 1:28 AM, David Lang <[email protected]> wrote: > Just a note that there is definantly something wrong with the variable > handling right now. I've got a hard to reproduce bug that I've been fighting > for the last month where messages from just a couple sources seem to trigger > corruption when sending messages out with an action that has it's own queue > and a custom template (output prior to the point is fine, but the message > send and output after shows corrupt data, occasionally a double free or > other corruption message) > > Some of the cleanup in the clang support branch seems to help some of it, > but the one box that I tested it on hasn't let me reproduce the problem > since, even with older versions :-( > > David Lang > > > > _______________________________________________ > 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. -- Regards, Janmejay http://codehunk.wordpress.com _______________________________________________ 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.
