Hi experienced QA folks, I have one libdbi test that runs under valgrind (as do many other tests). The goal here is to automatically detect misadressings and memory leaks.
The problem now is that different versions of libdbi have different memory "leaks"*. So on most current platforms, valgrind will report a memory. But that's a memory leak outside of my control. The usual approach is to use a suppression file. HOWEVER, the suppression file would need to be different for each platform/libdbi/dbserver combination. So this is not something I can ship as part of the testbench. Does anyone have an idea of how this could be solved? I will try now just to disable leak checking, so that the misaddressing "protection" is at least in place, but that's obviously a degradation of functionality. Help and feedback appreciated, Rainer * It's not a real leak in the case I am talking about, it has to do with when or when not libdbi calls mysql's thread shutdown functions. So this may even a problem that's solely related to the dbi driver layer. This is also nothing that needs to be reported to the libdbi project, because it definitely is fixed -- but as usual distros do not carry the fixed version. _______________________________________________ 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.
