parseok/unparser.stp tetscase fails on systemtap-20070630-snapshot. My environment is Systemtap-20070630 snapshot,elfutils-0.128 and kernel-2.6.22-rc7. When I executed this week tests, I found unparser.stp failing with below message. ============================================================ Running /home/systemtap/tmp/stap_testing_200707020915/src/testsuite/parseok/unparser.stp starting /home/systemtap/tmp/stap_testing_200707020915/src/testsuite/parseok/unparser.stp spawn2 /home/systemtap/tmp/stap_testing_200707020915/src/testsuite/parseok/unparser.stp /home/systemtap/tmp/stap_testing_200707020915/src/testsuite/../testsuite/parseok/eighteen.stp^M /home/systemtap/tmp/stap_testing_200707020915/src/testsuite/../testsuite/parseok/eighteen.stp^M parse error: expected literal string or number^M saw: operator '/' at <input>:7: parse error: expected literal string or number^M 13^M saw: operator '/' at <input>:7:13^M parse error: expected statement^M saw: <input> EOF^M 2 parse error(s).^M parse error: expected statement^M saw: <input> EOF^M 2 parse error(s).^M Pass 1: parse failed. Try again with more '-v' (verbose) options.^M Pass 1: parse failed. Try again with more '-v' (verbose) options.^M wait results: 6981 exp10 0 1 FAIL: parseok/unparser.stp ========================================================================
*** Bug 4723 has been marked as a duplicate of this bug. ***
Some of the code used to understand how the parsing and develop the coverage support was incorrectly checked in. The problem change has been removed. This correction has been checked into the cvs repository. The checked in change should resolve the problem.
This appears to be fixed -- please reopen if you have any more trouble.