> > > The weird part is that I've tried with "stock" 6.4.1 and I get the > > > same behavior. So either I'm doing something horribly wrong, or the > > > regression was introduced earlier. > > > > FYI: I can reproduce the problem. > > This seems to boil down to a problem with libestr. Which version of it > do you use (the bug seems to be present in the current version, but I'd > like to know what I am dealing with).
I blamed the wrong part. Rsyslog did provide an invalid stringlen to libestr, and that caused the problem. HOWEVER, this was introduced with the last patch. For me, plain 6.4.1 worked. You may want to verify that. In any case, this is the correction for the issue I saw (maybe we have two different issues here!): Patch: http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=09438518bb483d7bd6451311e3a9bed740b40893 It is probably a good idea to pull the v6-stable branch instead of just applying this patch, as it by now contains other commits as well. Please let me know if that works for you. 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 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.
