"no match" semantic error for some existing probe points

Frank Ch. Eigler fche@redhat.com
Tue Oct 17 20:55:00 GMT 2006


"Gui,Jian" <guij@cn.ibm.com> writes:

> In my ppc64/2.6.18:

> [...]
> prologue found function 'ptrace_disable' (naked) = 0xc000000000009db0
> pattern 'kernel' matches module 'kernel'
> semantic error: no match for probe point
> while: resolving probe point
> kernel.function("ptrace_disable@arch/powerpc/kernel/ptrace.c:246")
> [...]

Something strange is happening here, probably a translator bug.  The
"no match for probe point" message occurs if no "derived_probe"
instances get accumulated for a particular probe construct in the
script.  But it should have been created.  Debugging this may require
probing the messiest part of the translator: tapsets.cxx, starting
at(say) query_cu.

- FChE



More information about the Systemtap mailing list