no match while resolving probe point kernel.mark
Frank Ch. Eigler
fche@redhat.com
Sat Jan 17 16:45:00 GMT 2009
beginner966 <nitin966@gmail.com> writes:
> [...]
> I had put some static markers in the kernel, but later after recompilation,
> when I tried to run a script to probe them, following errors were generated:
> semantic error: no match while resolving probe point
> kernel.mark("__migrate_task_cpu_offline")
> [...]
OK.
> When I tried to use :
> # cat Module.markers
> Nothing was printed on the screen.
That explains the previous error.
> The kernel was compiled and installed.
Maybe there is a working build-side copy of Module.markers. Maybe
CONFIG_MARKERS were not turned on during the build. Maybe there was a
modpost bug that prevented the Module.markers file's correct creation.
- FChE
More information about the Systemtap
mailing list