This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: put probes on a specific line
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Li Guanglei <guanglei at cn dot ibm dot com>
- Cc: "systemtap at sourceware dot org" <systemtap at sourceware dot org>
- Date: 10 Oct 2006 12:39:52 -0400
- Subject: Re: put probes on a specific line
- References: <452B0EEB.5020206@cn.ibm.com>
Li Guanglei <guanglei@cn.ibm.com> writes:
> 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....). [...]
Not so: kernel.statement() accepts the same string-based specification
of a probe point as kernel.function() does:
kernel.statement("*@kernel/signal.c:734")
The "function" and "statement" terms are intentional and significant.
- FChE