rohc team mailing list archive

[Didier Barvaux <question216331@xxxxxxxxxxxxxxxxxxxxx>]

Question #216331 on rohc changed:
https://answers.launchpad.net/rohc/+question/216331

Didier Barvaux proposed the following answer:
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"

Let me know if it work. I'll then check for Valgrind version in order to
add the option if it is supported.

Regards,
Didier

-- 
You received this question notification because you are a member of ROHC
Team, which is an answer contact for rohc.