Hi -
In the queue on pcpfans.git:
branch fche/gcc5:
commit 704035986f5322cd96bee3c772ec570868a41c00
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Wed Feb 11 13:43:47 2015 -0500
pcp configury: gcc5 compatibility for -rdynamic
Fix a configury breakage due to gcc5 default warnings.
https://lists.fedoraproject.org/pipermail/devel/2015-February/207625.html
While in the vicinity fix a typo regarding struct dirent
field checking.
branch fche/pmmgr:
commit 4eb19a3c3ed5155c0d6b6ace2e27c57784f54729 (origin/fche/pmmgr)
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 b6c0b6fbb5393eb7405e18536f5d4cccd06efdaa
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 17075eacee1f35b7e4dbe30710053e49d26110ee
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.
branch fche/sasl-crash:
commit 22d1cc0b662b34f19fcdb9e5ba5af4e9005dbc40
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Tue Feb 10 11:26:39 2015 -0500
qa/720 test for memory sasl-authentication double-free
Add an item to the 720 testsuite that actually tests a sasl
authentication, not just a pcp-URL's syntactic parseability. This
test can trigger the memory double-free corrected in commit 4670799bf,
and a memory leak within cyrus-sasl (suppressed, reported as
RHBZ1191183).
commit 4670799bf275679fe4030d72f10003f7e15378fa
Author: Frank Ch. Eigler <fche@xxxxxxxxxx>
Date: Tue Feb 10 11:22:02 2015 -0500
Correct memory double-free of __pmGetAttrValue result
__pmGetAttrValue doesn't strdup its return value (and it's right
not to waste time that way). Its caller __pmAuthSecretCB thus
shouldn't free() it. (It'll be freed eventually during pcp-level
context-attribute cleanup.)
|