Comment 1 for bug 1096586

Your Valgrind version (3.5.0) seems to lack the --show-possibly-lost=yes option. Could you check that assertion in your Valgrind man page or with the following command:
 $ valgrind --help | grep show-possibly-lost

To workaround the problem, edit the test/valgrind.sh script to remove the --show-possibly-lost=yes option:

- run_test_with_valgrind()
- {
- OPTIONS="--tool=memcheck --trace-children=yes --track-fds=yes
- --leak-check=full --show-possibly-lost=yes --show-reachable=yes
- --malloc-fill=0xaa --free-fill=0x55"
+ run_test_with_valgrind()
+ {
+ OPTIONS="--tool=memcheck --trace-children=yes --track-fds=yes
+ --leak-check=full --show-reachable=yes
+ --malloc-fill=0xaa --free-fill=0x55"