From 07885a7317c11c71a73706fc8af3e32e7da9f4d8 Mon Sep 17 00:00:00 2001
From: wcohen <wcohen>
Date: Thu, 22 Sep 2005 18:53:25 +0000
Subject: Make documentation reflect reality.

---
 ChangeLog | 4 ++++
 stap.1.in | 6 +++---
 2 files changed, 7 insertions(+), 3 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 107d0f32..9e63c359 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2005-09-22  Will Cohen  <wcohen@redhat.com>
+
+	* stap.1.in: Correct sys_read alias example.
+
 2005-09-19  Frank Ch. Eigler  <fche@redhat.com>
 
 	* tapsets.cxx (*::emit_probe_entries): Handle busy-count correctly
diff --git a/stap.1.in b/stap.1.in
index d8185f61..0a0fb33d 100644
--- a/stap.1.in
+++ b/stap.1.in
@@ -293,13 +293,13 @@ operator.  In addition, the statement block that follows an alias
 definition is implicitly added as a prologue to any probe that refers
 to the alias.  For example:
 .SAMPLE
-probe syscall("read") = kernel.function("sys_read") {
+probe syscall.read = kernel.function("sys_read") {
   fildes = $fd
 }
 .ESAMPLE
 defines a new probe point
 .nh
-.IR syscall("read") ,
+.IR syscall.read ,
 .hy
 which expands to
 .nh
@@ -308,7 +308,7 @@ which expands to
 with the given assignment as a prologue.  Another probe definition
 may use the alias like this:
 .SAMPLE
-probe syscall("read") {
+probe syscall.read {
   printk ("reading fd=" . string (fildes))
 }
 .ESAMPLE
-- 
cgit