2015-03-16 20:01 GMT+01:00 Michael Biebl <[email protected]>: > 2015-03-16 14:06 GMT+01:00 Rainer Gerhards <[email protected]>: >> 2015-03-16 9:50 GMT+01:00 Rainer Gerhards <[email protected]>: >>> I think I get closer to a solutions. Looks like an "long long int" vs. >>> "int64_t" issue. I'll probably craft a small patch to test it out, which >>> would address at least most cases that failed. If that works out, there is >>> more to fix. >>> >>> Patch hopefully upcoming soon, but I thought I let you know in advance. >> >> It looks a bit crazy, not yet found the root cause. But the good thing >> is that I can reproduce it on Debian 7.8 32 bit. So I can now test >> myself... > > > Thanks Rainer! > If the test-suite results for the various architectures are useful, > I'll keep them enabled.
Yeah, I think it's very useful. This is a bug that otherwise would probably never have been captured (unfortunately it still hides successfully). side-note: would it be possible to have gdb and valgrind installed during the build? If so, the testbench can invoke some failure analysis if a test fails (depending on how it fails). 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.
