From: Li Guanglei <guanglei@cn.ibm.com>
To: "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: put probes on a specific line
Date: Tue, 10 Oct 2006 03:06:00 -0000 [thread overview]
Message-ID: <452B0EEB.5020206@cn.ibm.com> (raw)
Hi,
I ever thought that kernel.function("*@kernel/signal.c:734") will
put a probe on line 734. But after testing and reading the stapprobes
man page, that actually refers to any functions within the
"kernel/signal.c" file that span line 734, i.e, it equals to
kernel.function("send_signal"). So it seems to me the only way to put
probe on a specific line is to use kernel.statements(0x....). But this
is really troublesome and inconvenient for me. Sometimes I need to
visit some local variables and their valid location range is beyond
the function prologue, so using kernel.function(..@lineno) will
complain not finding that variable.
So I think it is really helpful if
kernel.function("*@kernel/signal.c:734") could act as I expected
before, that is, it will put a probe on line 734 of signal.c. Or else
SystemTap is of little help to probe somewhere inside a function and
visit some of its local variables, and I think these are important for
problem diagnosis.
- Guanglei
next reply other threads:[~2006-10-10 3:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 3:06 Li Guanglei [this message]
2006-10-10 16:40 ` Frank Ch. Eigler
2006-10-11 0:23 ` Li Guanglei
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=452B0EEB.5020206@cn.ibm.com \
--to=guanglei@cn.ibm.com \
--cc=systemtap@sourceware.org \
/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).