[Bug tapsets/4836] Interface changes in 2.6.23-rc1 causes tests to fail

["srinivasa at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From srinivasa at in dot ibm dot com  2007-07-24 09:31 -------
=========================================
Running
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/systemtap.samples/pfaults.exp
...
semantic error: no match for probe point while resolving probe point
kernel.function("__handle_mm_fault")^M
semantic error: no match for probe point while resolving probe point
kernel.function("__handle_mm_fault").return^M
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.^M
FAIL: pfaults (0)
=======================================================
Running
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentythree.stp
starting
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentythree.stp
spawn1 stap -gp4
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentythree.stp
semantic error: Expecting symbol or array index expression: identifier '$tsk' at
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentythree.stp:7:2^M
semantic error: Expecting symbol or array index expression: identifier '$tsk' at
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentythree.stp:7:2^M
semantic error: unknown type of arg to print operator: identifier '$tsk' at
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentythree.stp:8:30^M

semantic error: unknown type of arg to print operator: identifier '$tsk' at
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentythree.stp:8:30^M
Pass 3: translation failed.  Try again with more '-v' (verbose) options.^M

Pass 3: translation failed.  Try again with more '-v' (verbose) options.^M
wait results: 376 exp10 0 1
FAIL: buildok/twentythree.stp
========================================================
Running
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentytwo.stp
starting
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentytwo.stp
spawn1 stap -p4
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/twentytwo.stp
semantic error: field 'timestamp' not found (alternatives: state stack usage
flags ptrace lock_dept
h prio static_prio normal_prio run_list sched_class se ioprio btrace_seq policy
cpus_allowed time_s
lice sched_info tasks ptrace_children ptrace_list mm active_mm binfmt exit_
..................................
Pass 2: analysis failed.  Try again with more '-v' (verbose) options.^M

Pass 2: analysis failed.  Try again with more '-v' (verbose) options.^M
wait results: 380 exp10 0 1
FAIL: buildok/twentytwo.stp
=====================================================
Running
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/memory.stp
starting
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/memory.stp
spawn1 stap -p4
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/memory.stp
semantic error: no match for probe point while resolving probe point
kernel.function("__handle_mm_fault")^M
semantic error: no match for probe point while resolving probe point
kernel.function("__handle_mm_fault")^M
semantic error: no match for probe point while resolving probe point vm.pagefault^M

semantic error: no match for probe point while resolving probe point vm.pagefault^M
semantic error: no match for probe point while resolving probe point
kernel.function("__handle_mm_fault").return^M

semantic error: no match for probe point while resolving probe point
kernel.function("__handle_mm_fault").return^M
semantic error: no match for probe point while resolving probe point
vm.pagefault.return^M

semantic error: no match for probe point while resolving probe point
vm.pagefault.return^M
===================================================================
Running
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/task_test.stp
starting
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/task_test.stp
spawn1 stap -p4
/home/systemtap/tmp/stap_testing_200707230621/src/testsuite/buildok/task_test.stp
Pass 4: compilation failed.  Try again with more '-v' (verbose) options.^M
Pass 4: compilation failed.  Try again with more '-v' (verbose) options.^M
wait results: 30922 exp10 0 1
FAIL: buildok/task_test.stp
===========================================================





-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4836

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.