From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26698 invoked by alias); 21 Aug 2013 10:13:23 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 26686 invoked by uid 89); 21 Aug 2013 10:13:23 -0000 X-Spam-SWARE-Status: No, score=-6.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_HOSTKARMA_W,RCVD_IN_HOSTKARMA_WL,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Wed, 21 Aug 2013 10:13:22 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r7LADLPN022994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 21 Aug 2013 06:13:21 -0400 Received: from redhat.com.redhat.com (dhcp-25-208.brq.redhat.com [10.34.25.208]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r7LADJaQ016450 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 21 Aug 2013 06:13:20 -0400 From: Miroslav Franc To: systemtap@sourceware.org Subject: Few typos in language reference and tutorial X-Yow: I think I am an overnight sensation right now!! Date: Wed, 21 Aug 2013 10:13:00 -0000 Message-ID: <87mwob8i7z.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2 (gnu/linux) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" X-Virus-Found: No X-SW-Source: 2013-q3/txt/msg00163.txt.bz2 --=-=-= Content-Type: text/plain Content-length: 166 Hi, I was going through language reference and tutorial and found some typos. Not sure what is correct procedure here. Should I file a bug or is a patch enough? --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=langref-tutorial-typos.diff Content-Description: Few typos in langref and tutorial Content-length: 2308 diff --git a/doc/langref.tex b/doc/langref.tex index caf9016..d0c0508 100644 --- a/doc/langref.tex +++ b/doc/langref.tex @@ -94,7 +94,7 @@ problem. SystemTap was designed to eliminate the need for a developer to go through the tedious instrument, recompile, install, and reboot sequence normally required to collect this kind of data. To do this, it provides a simple command-line interface and scripting language for writing -instrumenation for both kernel and user space. +instrumentation for both kernel and user space. With SystemTap, developers, system administrators, and users can easily write scripts that gather and manipulate system data that is otherwise unavailable from standard Linux tools. Users of SystemTap will find it to be a significant @@ -989,8 +989,8 @@ General syntax: \begin{vindent} \begin{verbatim} -kernel.function("func[@file]" -module("modname").function("func[@file]" +kernel.function("func[@file]") +module("modname").function("func[@file]") \end{verbatim} \end{vindent} Examples: diff --git a/doc/tutorial.tex b/doc/tutorial.tex index a5a4c17..7b4fde5 100644 --- a/doc/tutorial.tex +++ b/doc/tutorial.tex @@ -470,7 +470,7 @@ Systemtap allows limited dereferencing of such pointer chains. Two functions, \verb+user_string+ and \verb+kernel_string+, can copy \verb+char *+ target variables into systemtap strings. Figure~\ref{fig:inode-watch} demonstrates one way to monitor a -particular file (identifed by device number and inode number). +particular file (identified by device number and inode number). The script selects the appropriate variants of \verb+dev_nr+ and\verb+inode_nr+ based on the kernel version. This example also demonstrates passing numeric command-line arguments @@ -569,7 +569,7 @@ indexed by some tuple of thread numbers, processor ids, names, time, and so on. Systemtap offers associative arrays for this purpose. These arrays are implemented as hash tables with a maximum size that is fixed at startup. Because they are too large to be created -dynamically for inidividual probes handler runs, they must be declared +dynamically for individual probes handler runs, they must be declared as global. \nomenclature{array}{A global \verb+[+$k_1,k_2,\ldots,k_n\verb+]+\rightarrow value$ associative lookup table, with a string, --=-=-= Content-Type: text/plain Content-length: 199 -- Miroslav Franc, QE, Tool Chain mfranc@redhat.com "During smoke testing you are waiting for magic smoke to appear whereas during sanity testing you are praying for your sanity." --=-=-=--