summaryrefslogtreecommitdiffstats
path: root/doc/tutorial.tex
diff options
context:
space:
mode:
authorwenji <wjhuang@dhcp-beijing-cdc-10-182-120-233.cn.oracle.com>2008-04-13 22:50:18 -0400
committerwenji <wjhuang@dhcp-beijing-cdc-10-182-120-233.cn.oracle.com>2008-04-13 22:50:18 -0400
commitbd10b81c06a0102ac10617da2f368fcc168fc15e (patch)
tree07c4878e3eaf77801d5104c2f6c498cfff9e3bbd /doc/tutorial.tex
parentd58c66bfef5cfa7267ced03db11928fd5c78ba9c (diff)
parentf7e07777e033e580351dc6886ab7dbdddd9839fe (diff)
downloadsystemtap-steved-bd10b81c06a0102ac10617da2f368fcc168fc15e.tar.gz
systemtap-steved-bd10b81c06a0102ac10617da2f368fcc168fc15e.tar.xz
systemtap-steved-bd10b81c06a0102ac10617da2f368fcc168fc15e.zip
Merge branch 'master' of ssh://wenji@sources.redhat.com/git/systemtap
Diffstat (limited to 'doc/tutorial.tex')
-rw-r--r--doc/tutorial.tex6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/tutorial.tex b/doc/tutorial.tex
index 58673467..3a04900b 100644
--- a/doc/tutorial.tex
+++ b/doc/tutorial.tex
@@ -175,8 +175,10 @@ in a source file, say \verb+net/socket.c+ in the kernel. The
systemtap examines the kernel's debugging information to relate object
code to source code. It works like a debugger: if you can name or
place it, you can probe it. Use
-\verb+kernel.function("*@net/socket.c")+ for the function entries, and
-\verb+kernel.function("*@net/socket.c").return+ for the exits. Note
+\verb+kernel.function("*@net/socket.c").call+ for the function
+entries\footnote{Without the {\tt .call} qualifier, inlined function
+instances are also probed, but they have no corresponding {\tt .return}.},
+and \verb+kernel.function("*@net/socket.c").return+ for matching exits. Note
the use of wildcards in the function name part, and the subsequent
\verb+@FILENAME+ part. You can also put wildcards into the file name,
and even add a colon (\verb+:+) and a line number, if you want to