This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
pfaults.stp fix (for 2.6.13 and beyond)
- From: Badari Pulavarty <pbadari at us dot ibm dot com>
- To: systemtap at sources dot redhat dot com
- Date: Wed, 05 Oct 2005 08:21:02 -0700
- Subject: pfaults.stp fix (for 2.6.13 and beyond)
Hi,
handle_mm_fault() became a inline function now (2.6.13 & beyond).
So pfaults.stp should use __handle_mm_fault() instead.
Thanks,
Badari
[root@elm3b23 systemtap.samples]# stap -g pfaults.stp
semantic error: no match for probe point
while: resolving probe point kernel.function("handle_mm_fault")
semantic error: no match for probe point
while: resolving probe point kernel.function
("handle_mm_fault").return
Pass 2: analysis failed. Try again with '-v' (verbose) option.
--- tests/testsuite/systemtap.samples/pfaults.stp 2005-10-05 08:13:29.000000000 -0700
+++ tests.new/testsuite/systemtap.samples/pfaults.stp 2005-10-05 08:11:27.000000000 -0700
@@ -2,7 +2,7 @@
global pidnames, faults, fault_types
-probe kernel.function("handle_mm_fault") {
+probe kernel.function("__handle_mm_fault") {
# Maintain a pid-to-execname mapping. This logic should get transplanted
# into a tapset script that is automatically included upon reference to
@@ -15,7 +15,7 @@ probe kernel.function("handle_mm_fault")
# (needed only until bug 1132 supports $retvalue)
function get_retvalue:long () %{ THIS->__retvalue = fetch_register(0); %}
-probe kernel.function("handle_mm_fault").return {
+probe kernel.function("__handle_mm_fault").return {
fault_types [pid(), get_retvalue()] ++
}