From: fche@redhat.com (Frank Ch. Eigler)
To: Vara Prasad <prasadav@us.ibm.com>
Cc: SystemTAP <systemtap@sources.redhat.com>
Subject: Re: [Fwd: Re: [Bug translator/3534] New: support wildcarded linenumber probe syntax]
Date: Sun, 19 Nov 2006 11:12:00 -0000 [thread overview]
Message-ID: <y0mk61s635k.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <455D55C9.3070709@us.ibm.com>
varap wrote:
> [...] If i got your above idea correct, is this proposal is to
> support tracing of a function without tracing other functions it
> calls. [...]
Yes, that would be one use. Or one could monitor a variable for
change that is suspected to occur someplace within the function: a
manual version of a watchpoint. One might get basic-block coverage or
branch probability profiles:
probe kernel.statements("the_function@*:*") {
hits[lineno()] ++ # lineno() in future, or pc() now
}
global hits
probe end {
foreach (l+ in lineno)
printf ("%d %d\n", l, hits[l]);
}
- FChE
prev parent reply other threads:[~2006-11-18 18:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 12:35 Vara Prasad
2006-11-19 11:12 ` Frank Ch. Eigler [this message]
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=y0mk61s635k.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=prasadav@us.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).