From a6f1ed2e550699722ee8483018cb9230c62d1ace Mon Sep 17 00:00:00 2001 From: ddomingo Date: Thu, 9 Oct 2008 14:14:50 +1000 Subject: added Counting Function Calls Made, other minor edits --- doc/SystemTap_Beginners_Guide/en-US/Scripts.xml | 2 +- .../en-US/Useful_Scripts-functioncalls.xml | 80 ++++++++++++++++++++++ .../en-US/Useful_SystemTap_Scripts.xml | 2 +- 3 files changed, 82 insertions(+), 2 deletions(-) create mode 100644 doc/SystemTap_Beginners_Guide/en-US/Useful_Scripts-functioncalls.xml (limited to 'doc/SystemTap_Beginners_Guide') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Scripts.xml b/doc/SystemTap_Beginners_Guide/en-US/Scripts.xml index 7914e79c..92dd8f1c 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Scripts.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Scripts.xml @@ -430,7 +430,7 @@ probe syscall.* { When is run with the argument -x process ID, it watches all system calls (as specified by the event syscall.*) and prints out the name of all system calls made by the specified process. - This has the same effect as specifying if (pid() == process ID each time you wish to target a specific process. However, using target() makes it easier for you to re-use the script, giving you the ability to simply pass a process ID as an argument each time you wish to run the script (e.g. stap targetexample.stp -x process ID). + This has the same effect as specifying if (pid() == process ID) each time you wish to target a specific process. However, using target() makes it easier for you to re-use the script, giving you the ability to simply pass a process ID as an argument each time you wish to run the script (e.g. stap targetexample.stp -x process ID).