public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: "Gui,Jian" <guij@cn.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: "no match" semantic error for some existing probe points
Date: Tue, 17 Oct 2006 20:55:00 -0000	[thread overview]
Message-ID: <y0mlknewtle.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <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

  reply	other threads:[~2006-10-17 20:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 10:17 Gui,Jian
2006-10-17 20:55 ` Frank Ch. Eigler [this message]
2006-10-18  4:00   ` Gui,Jian
2006-10-19  7:40     ` Gui,Jian
2006-10-24 17:58       ` Roland McGrath
2006-10-30  6:12         ` Gui,Jian
2006-10-30 22:07           ` Roland McGrath
2006-11-01  7:03             ` Alexandre Oliva
2006-11-01 12:32               ` Gui,Jian
2006-11-07  7:52                 ` Alexandre Oliva
2006-11-07 14:34                   ` Gui,Jian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=y0mlknewtle.fsf@ton.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=guij@cn.ibm.com \
    --cc=systemtap@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).