removed man pages

author: lberk <lberk> 2013-02-26 17:31:32 +0000
committer: lberk <lberk> 2013-02-26 17:31:32 +0000
commit: dc082b04a33a957c89a7b5ff83933a7ba5ee4874 (patch)
tree: 001e0d3ff123680f6d8280e66d682ad0b0f1f728 /SystemTap_Beginners_Guide/userspace-probing.html
parent: add new langref/*.html (diff)
1 files changed, 1 insertions, 1 deletions
diff --git a/SystemTap_Beginners_Guide/userspace-probing.html b/SystemTap_Beginners_Guide/userspace-probing.html
index 2e91a8fa..2ebc90f3 100644
--- a/SystemTap_Beginners_Guide/userspace-probing.html
+++ b/SystemTap_Beginners_Guide/userspace-probing.html
@@ -13,7 +13,7 @@ As root, or a member of the 'root' group, run
 "make -C /usr/share/systemtap/runtime/uprobes".
 Pass 4: compilation failed. Try again with another '--vp 0001' option.</pre><div class="para">
 If this occurs, you need to generate a uprobes.ko module for the kernel as directed.
- </div><div class="section" id="uevents"><div class="titlepage"><div><div><h2 class="title" id="uevents">4.1. User-Space Events</h2></div></div></div><a id="idp61786784" class="indexterm"></a><div class="para">
+ </div><div class="section" id="uevents"><div class="titlepage"><div><div><h2 class="title" id="uevents">4.1. User-Space Events</h2></div></div></div><a id="idp58293168" class="indexterm"></a><div class="para">
 All user-space event probes begin with <span class="emphasis"><em>process</em></span>. The process events can be limited to a specific running process by specifying the process ID. The process events can also be limited to monitoring a particular executable by specifying the path to executable (PATH). SystemTap makes use of the <code class="command">PATH</code> environment variable, so both the name used on the command-line to start the executable and the absolute path to the executable can be used. Several of user-space probe events limit their scope to a particular executable name (PATH) because SystemTap must use debug information to statically analyzed where to places the probes, but for many user-space probes events the process ID and executable name are optional. Any <code class="command">process</code> event in the list below that include process ID or the path to the executable must include those arguments. The process ID and path to the executable are optional for the <code class="command">process</code> events that do not list them:
 </div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">process("<em class="replaceable"><code>PATH</code></em>").function("<em class="replaceable"><code>function</code></em>")</span></dt><dd><div class="para">
 The entry to the user-space function <em class="replaceable"><code>function</code></em> for the executable <em class="replaceable"><code>PATH</code></em>. This event is the user-space analogue of the <code class="command">kernel.function("<em class="replaceable"><code>function</code></em>")</code> event. It allows wildcards for the function <em class="replaceable"><code>function</code></em> and <code class="command">.return</code> suffix.
author	lberk <lberk>	2013-02-26 17:31:32 +0000
committer	lberk <lberk>	2013-02-26 17:31:32 +0000
commit	dc082b04a33a957c89a7b5ff83933a7ba5ee4874 (patch)
tree	001e0d3ff123680f6d8280e66d682ad0b0f1f728 /SystemTap_Beginners_Guide/userspace-probing.html
parent	add new langref/*.html (diff)

diff --git a/SystemTap_Beginners_Guide/userspace-probing.html b/SystemTap_Beginners_Guide/userspace-probing.html index 2e91a8fa..2ebc90f3 100644 --- a/SystemTap_Beginners_Guide/userspace-probing.html +++ b/SystemTap_Beginners_Guide/userspace-probing.html
@@ -13,7 +13,7 @@ As root, or a member of the 'root' group, run
13	"make -C /usr/share/systemtap/runtime/uprobes".	13	"make -C /usr/share/systemtap/runtime/uprobes".
14	Pass 4: compilation failed. Try again with another '--vp 0001' option.</pre><div class="para">	14	Pass 4: compilation failed. Try again with another '--vp 0001' option.</pre><div class="para">
15	If this occurs, you need to generate a uprobes.ko module for the kernel as directed.	15	If this occurs, you need to generate a uprobes.ko module for the kernel as directed.
16	</div><div class="section" id="uevents"><div class="titlepage"><div><div><h2 class="title" id="uevents">4.1. User-Space Events</h2></div></div></div><a id="idp61786784" class="indexterm"></a><div class="para">	16	</div><div class="section" id="uevents"><div class="titlepage"><div><div><h2 class="title" id="uevents">4.1. User-Space Events</h2></div></div></div><a id="idp58293168" class="indexterm"></a><div class="para">
17	All user-space event probes begin with <span class="emphasis"><em>process</em></span>. The process events can be limited to a specific running process by specifying the process ID. The process events can also be limited to monitoring a particular executable by specifying the path to executable (PATH). SystemTap makes use of the <code class="command">PATH</code> environment variable, so both the name used on the command-line to start the executable and the absolute path to the executable can be used. Several of user-space probe events limit their scope to a particular executable name (PATH) because SystemTap must use debug information to statically analyzed where to places the probes, but for many user-space probes events the process ID and executable name are optional. Any <code class="command">process</code> event in the list below that include process ID or the path to the executable must include those arguments. The process ID and path to the executable are optional for the <code class="command">process</code> events that do not list them:	17	All user-space event probes begin with <span class="emphasis"><em>process</em></span>. The process events can be limited to a specific running process by specifying the process ID. The process events can also be limited to monitoring a particular executable by specifying the path to executable (PATH). SystemTap makes use of the <code class="command">PATH</code> environment variable, so both the name used on the command-line to start the executable and the absolute path to the executable can be used. Several of user-space probe events limit their scope to a particular executable name (PATH) because SystemTap must use debug information to statically analyzed where to places the probes, but for many user-space probes events the process ID and executable name are optional. Any <code class="command">process</code> event in the list below that include process ID or the path to the executable must include those arguments. The process ID and path to the executable are optional for the <code class="command">process</code> events that do not list them:
18	</div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">process("<em class="replaceable"><code>PATH</code></em>").function("<em class="replaceable"><code>function</code></em>")</span></dt><dd><div class="para">	18	</div><div class="variablelist"><dl><dt class="varlistentry"><span class="term">process("<em class="replaceable"><code>PATH</code></em>").function("<em class="replaceable"><code>function</code></em>")</span></dt><dd><div class="para">
19	The entry to the user-space function <em class="replaceable"><code>function</code></em> for the executable <em class="replaceable"><code>PATH</code></em>. This event is the user-space analogue of the <code class="command">kernel.function("<em class="replaceable"><code>function</code></em>")</code> event. It allows wildcards for the function <em class="replaceable"><code>function</code></em> and <code class="command">.return</code> suffix.	19	The entry to the user-space function <em class="replaceable"><code>function</code></em> for the executable <em class="replaceable"><code>PATH</code></em>. This event is the user-space analogue of the <code class="command">kernel.function("<em class="replaceable"><code>function</code></em>")</code> event. It allows wildcards for the function <em class="replaceable"><code>function</code></em> and <code class="command">.return</code> suffix.