From a9f3ab125303a2e89dd3c17b39f26e1d2c428fa5 Mon Sep 17 00:00:00 2001
From: "Frank Ch. Eigler" <fche@elastic.org>
Date: Sun, 13 Apr 2008 17:48:16 -0400
Subject: Clarify .function().call vs .function as tutorial footnote

---
 doc/tutorial.tex | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

(limited to 'doc/tutorial.tex')

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
-- 
cgit 

