rohc

Tests use an unsupported option for Valgrind <= 3.6.0

Bug #1096586 reported by Didier Barvaux
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rohc
Status tracked in Rohc-main
1.3.x
Invalid
Undecided
Didier Barvaux
rohc 1.3.5
1.4.x
Invalid
Undecided
Didier Barvaux
rohc 1.4.3
Rohc-1.5.x
Fix Released
Low
Didier Barvaux
rohc 1.5.2
Rohc-main
Fix Released
Low
Didier Barvaux
rohc 1.6.0

Bug Description

'make check' is failing some testcases due to valgrind issue:

FAIL: test_feedback2_ack_smallcid_smallsn_crc.sh
FAIL: test_feedback2_ack_smallcid_largesn_sn-crc.sh
FAIL: test_feedback2_ack_largecid_largesn_sn-crc.sh
FAIL: test_feedback2_ack_largecid_smallsn_crc.sh
============================================
4 of 4 tests failed
See test/functional/feedback2/test-suite.log
Please report to http://rohc-lib.org/
============================================
make[5]: *** [test-suite.log] Error 1
make[5]: Leaving directory `/home/rgupta/rohc/rohc-1.5.0/test/functional/feedback2'
make[4]: *** [check-TESTS] Error 2
make[4]: Leaving directory `/home/rgupta/rohc/rohc-1.5.0/test/functional/feedback2'

[Raman] The file test/functional/feedback2/test-suite.log says:-

packet #16:
 decompression is successful
 5-byte feedback generated
 Add-CID found
 FEEDBACK-2 is a ack feedback as expected
 SN (or a part of it) = 0x0fff
 2-byte CRC option found
valgrind: Bad option '--show-possibly-lost=yes'; aborting.
valgrind: Use --help for more information.
test failed inside valgrind (exit code 1)
grep: /tmp/valgrind_500_7cf27bf163527c26c18cb48653bc9292_1355137496.xml: No such file or directory
XSL transformation failed:
command: /usr/bin/xsltproc "./../../valgrind.xsl" "/tmp/valgrind_500_7cf27bf163527c26c18cb48653bc9292_1355137496.xml.filtered"
/tmp/valgrind_500_7cf27bf163527c26c18cb48653bc9292_1355137496.xml.filtered:1: parser error : StartTag: invalid element name
</valgrindoutput>
 ^
/tmp/valgrind_500_7cf27bf163527c26c18cb48653bc9292_1355137496.xml.filtered:1: parser error : Extra content at the end of the document
</valgrindoutput>
 ^
unable to parse /tmp/valgrind_500_7cf27bf163527c26c18cb48653bc9292_1355137496.xml.filtered

FAIL: test_feedback2_ack_smallcid_largesn_sn-crc.sh (exit: 1)
=============================================================

packet #1:
 decompression is successful
 6-byte feedback generated
 FEEDBACK-2 is a ack feedback as expected
 SN (or a part of it) = 0x0010
 2-byte SN option found
 2-byte CRC option found
valgrind: Bad option '--show-possibly-lost=yes'; aborting.
valgrind: Use --help for more information.
test failed inside valgrind (exit code 1)
grep: /tmp/valgrind_500_d70b0913ed907b3aa3108d45977e5760_1355137498.xml: No such file or directory
XSL transformation failed:
command: /usr/bin/xsltproc "./../../valgrind.xsl" "/tmp/valgrind_500_d70b0913ed907b3aa3108d45977e5760_1355137498.xml.filtered"
/tmp/valgrind_500_d70b0913ed907b3aa3108d45977e5760_1355137498.xml.filtered:1: parser error : StartTag: invalid element name
</valgrindoutput>
 ^
/tmp/valgrind_500_d70b0913ed907b3aa3108d45977e5760_1355137498.xml.filtered:1: parser error : Extra content at the end of the document
</valgrindoutput>
 ^
unable to parse /tmp/valgrind_500_d70b0913ed907b3aa3108d45977e5760_1355137498.xml.filtered

FAIL: test_feedback2_ack_largecid_largesn_sn-crc.sh (exit: 1)
=============================================================

packet #1:
 decompression is successful
 7-byte feedback generated
 large CID found
 FEEDBACK-2 is a ack feedback as expected
 SN (or a part of it) = 0x0010
 2-byte SN option found
 2-byte CRC option found
valgrind: Bad option '--show-possibly-lost=yes'; aborting.
valgrind: Use --help for more information.
test failed inside valgrind (exit code 1)
grep: /tmp/valgrind_500_b771aedac472f7bd48b0ff49bc3a8b4c_1355137501.xml: No such file or directory
XSL transformation failed:
command: /usr/bin/xsltproc "./../../valgrind.xsl" "/tmp/valgrind_500_b771aedac472f7bd48b0ff49bc3a8b4c_1355137501.xml.filtered"
/tmp/valgrind_500_b771aedac472f7bd48b0ff49bc3a8b4c_1355137501.xml.filtered:1: parser error : StartTag: invalid element name
</valgrindoutput>
 ^
/tmp/valgrind_500_b771aedac472f7bd48b0ff49bc3a8b4c_1355137501.xml.filtered:1: parser error : Extra content at the end of the document
</valgrindoutput>
 ^
unable to parse /tmp/valgrind_500_b771aedac472f7bd48b0ff49bc3a8b4c_1355137501.xml.filtered

FAIL: test_feedback2_ack_largecid_smallsn_crc.sh (exit: 1)
==========================================================

packet #1:
 decompression is successful
 5-byte feedback generated
 large CID found
 FEEDBACK-2 is a ack feedback as expected
 SN (or a part of it) = 0x0100
 2-byte CRC option found
valgrind: Bad option '--show-possibly-lost=yes'; aborting.
valgrind: Use --help for more information.
test failed inside valgrind (exit code 1)
grep: /tmp/valgrind_500_6828eeebb004b6b4f434ecebb47ec60b_1355137503.xml: No such file or directory
XSL transformation failed:
command: /usr/bin/xsltproc "./../../valgrind.xsl" "/tmp/valgrind_500_6828eeebb004b6b4f434ecebb47ec60b_1355137503.xml.filtered"
/tmp/valgrind_500_6828eeebb004b6b4f434ecebb47ec60b_1355137503.xml.filtered:1: parser error : StartTag: invalid element name
</valgrindoutput>
 ^
/tmp/valgrind_500_6828eeebb004b6b4f434ecebb47ec60b_1355137503.xml.filtered:1: parser error : Extra content at the end of the document
</valgrindoutput>
 ^
unable to parse /tmp/valgrind_500_6828eeebb004b6b4f434ecebb47ec60b_1355137503.xml.filtered

[Raman]: My valgrind version is 3.5.0

Tags: tests valgrind
Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

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"

tags: added: tests valgrind
Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Branch 1.3.x does not support Valgrind at all, so it is not affected by the problem.

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Branch 1.4.x does not support Valgrind at all, so it is not affected by the problem.

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Branch 1.5.x is affected.

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Main branch is affected.

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Fixed in branch 1.5.x. See http://bazaar.launchpad.net/~didier-barvaux/rohc/1.5.x/revision/560

Revision history for this message
Didier Barvaux (didier-barvaux) wrote :

Fixed in main branch. See http://bazaar.launchpad.net/~didier-barvaux/rohc/main/revision/669

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.