This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: "no match" semantic error for some existing probe points
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: "Gui,Jian" <guij at cn dot ibm dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: 17 Oct 2006 16:55:09 -0400
- Subject: Re: "no match" semantic error for some existing probe points
- References: <4534AD25.1050205@cn.ltcfwd.linux.ibm.com>
"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