Hi -
> [..]
> A permanent QA test helps beyond just the immediate concern, of course;
> for the next person hacking on pmmgr & accidentally introducing a leak,
> so please do give it some thought.
Enjoy pcpfans.git fche/pmmgr:
commit 0c9496a4fbd08e7b7c292a9097f900e39f182c04
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Thu Feb 5 21:40:54 2015 -0500
qa/666: use $_valgrind_clean_assert for pmmgr under microscope
commit b32ac025a46db98a5f0c7afdbb137087766e7027
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Thu Feb 5 21:38:48 2015 -0500
qa/common.check: introduce $_valgrind_clean_assert
This is a variable which a normal test case can casually insert
ahead of an invocation of some random pcp or other program. It
may expand to nothing, or to a "valgrind -q ..." prefix. Using
it thusly:
$_valgrind_clean_assert CMD ARGS ...
is a nop, unless there are unsuppressed valgrind errors.
commit d3202e24be3b03e62a8b2c6cec2e8fa59216a6c1
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Fri Jan 23 21:36:01 2015 -0500
pmmgr: build fix for older g++
std::map::at turns out to be a c++11 facility.
Use the equivalent but wordier find()->second instead.
|