Attachment 1234 Details for Bug 3094 – fix for the bug

[patch] fix for the bug

systemtap-manpages.diff (text/plain), 8.63 KB, created by Eugeniy Meshcheryakov on 2006-08-19 18:18:25 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Eugeniy Meshcheryakov

Created: 2006-08-19 18:18:25 UTC

Size: 8.63 KB

patch

obsolete

>diff -ruN src-old/lket.5.in src/lket.5.in
>--- src-old/lket.5.in	2006-07-19 14:50:03.000000000 +0200
>+++ src/lket.5.in	2006-07-22 17:00:03.000000000 +0200
>@@ -204,10 +204,10 @@
> is the combination of:
> 
> .SAMPLE
>-((cmd->device->host->host_no & 0xFF) << 24) |
>-((cmd->device->channel & 0xFF) << 16) |
>-((cmd->device->lun & 0xFF) << 8) |
>-(cmd->device->id & 0xFF)
>+((cmd\->device\->host\->host_no & 0xFF) << 24) |
>+((cmd\->device\->channel & 0xFF) << 16) |
>+((cmd\->device\->lun & 0xFF) << 8) |
>+(cmd\->device\->id & 0xFF)
> .ESAMPLE
> 
> .TP
>@@ -483,25 +483,25 @@
> 
> By default, LKET will log the trace data in binary format.
> 
>-To get a better performance for binary tracing, the "-b" option should
>-be turned on for stap and thus -M option has to be added to stop stpd
>+To get a better performance for binary tracing, the "\-b" option should
>+be turned on for stap and thus \-M option has to be added to stop stpd
> merging per-cpu files.
> 
> You could use the command 
>-.I lket-b2a
>+.I lket\-b2a
> to convert the binary trace data 
> generated by LKET into readable data in ascii format.
> 
>-.I lket-b2a
>+.I lket\-b2a
> uses the pre-cpu binary trace data files as inputs, and generates
> an output file named 
> .I lket.out
>-You should use "stap -b -M" with LKET to get those pre-cpu files
>+You should use "stap \-b \-M" with LKET to get those pre-cpu files
> (stpd_cpu*) before using it.
> 
> If you want LKET to log trace data in ASCII format directly, you should:
> .SAMPLE
>-stap -D ASCII_TRACE ...
>+stap \-D ASCII_TRACE ...
> .ESAMPLE
> 
> .SH EVENT REGISTER
>@@ -572,9 +572,9 @@
> 
> LKET provides a way to do this without modifying the codes in
> the tapset of that event hook. You can simply use printf to trace
>-extra data. For example, supposing you want to trace sk_buff->mac_len
>-and sk_buff->priority besides the sk_buff->len, sk_buff->protocol and
>-sk_buff->truesize for the 
>+extra data. For example, supposing you want to trace sk_buff\->mac_len
>+and sk_buff\->priority besides the sk_buff\->len, sk_buff\->protocol and
>+sk_buff\->truesize for the 
> .B netdev 
> event hooks:
> 
>@@ -586,7 +586,7 @@
> }
> probe addevent.netdev.transmit
> {
>-    printf("%4b%4b", $skb->mac_len, $skb->priority)
>+    printf("%4b%4b", $skb\->mac_len, $skb\->priority)
> }
> .ESAMPLE
> 
>@@ -596,16 +596,16 @@
> 
> .TP
> To turn on all event hooks:
>-stap -e "probe addevent.* {}" -bM
>+stap \-e "probe addevent.* {}" \-bM
> .TP
> To probe syscall:
>-stap -e "probe addevent.syscall {}" -bM
>+stap \-e "probe addevent.syscall {}" \-bM
> .TP
> To only probe syscall.entry:
>-stap -e "probe addevent.syscall.entry {}" -bM
>+stap \-e "probe addevent.syscall.entry {}" \-bM
> .TP
> To probe netdev transmition and log extra data of mac_len and priority:
>-stap -e "probe addevent.netdev.transmit { printf(\\"%4b%4b\\", $skb->mac_len, $skb->priority) }" -bM
>+stap \-e "probe addevent.netdev.transmit { printf(\\"%4b%4b\\", $skb\->mac_len, $skb\->priority) }" \-bM
> 
> .SH SEE ALSO
> .IR stap (1)
>diff -ruN src-old/stap.1.in src/stap.1.in
>--- src-old/stap.1.in	2006-06-05 21:45:56.000000000 +0200
>+++ src/stap.1.in	2006-07-22 16:57:28.000000000 +0200
>@@ -78,7 +78,7 @@
> The systemtap translator supports the following options.  Any other option
> prints a list of supported options.
> .\" undocumented for now:
>-.\" -t test mode
>+.\" \-t test mode
> .TP
> .B \-v
> Increase verbosity.  Produce a larger volume of informative (?) output
>@@ -203,7 +203,7 @@
> .PP
> If the first part is the identifier
> .BR kernel_vr " or " kernel_v
>-to refer to the kernel version number, with ("2.6.13-1.322FC3smp") or
>+to refer to the kernel version number, with ("2.6.13\-1.322FC3smp") or
> without ("2.6.13") the release code suffix, then
> the second part is one of the six standard numeric comparison operators
> .BR < ", " <= ", " == ", " != ", " > ", and " >= ,
>@@ -235,7 +235,7 @@
> .SAMPLE
> probe kernel.function ( 
>   %( kernel_v <= "2.6.12" %? "__mm_do_fault" %: 
>-     %( kernel_vr == "2.6.13-1.8273FC3smp" %? "do_page_fault" %:
>+     %( kernel_vr == "2.6.13\-1.8273FC3smp" %? "do_page_fault" %:
>         UNSUPPORTED %) %)
> ) { /* ... */ }
> 
>@@ -309,7 +309,7 @@
> Loop over each element of the named global array, assigning current
> key to VAR.  The array may not be modified within the statement.
> By adding a single 
>-.BR + " or " -
>+.BR + " or " \-
> operator after the VAR or the ARRAY identifier, the iteration will
> proceed in a sorted order, by ascending or descending index or value.
> .TP
>@@ -349,20 +349,20 @@
> detected and results in an error.
> .TP
> binary numeric operators
>-.B * / % + - >> << & ^ | && ||
>+.B * / % + \- >> << & ^ | && ||
> .TP
> binary string operators
> .B .
> (string concatenation)
> .TP
> numeric assignment operators
>-.B = *= /= %= += -= >>= <<= &= ^= |=
>+.B = *= /= %= += \-= >>= <<= &= ^= |=
> .TP
> string assignment operators
> .B = .=
> .TP
> unary numeric operators
>-.B + - ! ~ ++ -- 
>+.B + \- ! ~ ++ \-\- 
> .TP
> binary numeric or string comparison operators
> .B < > <= >= == !=
>@@ -604,11 +604,11 @@
> Here are some examples:
> .SAMPLE
> function add_one (val) %{
>-  THIS->__retvalue = THIS->val + 1;
>+  THIS\->__retvalue = THIS\->val + 1;
> %}
> function add_one_str (val) %{
>-  strlcpy (THIS->__retvalue, THIS->val, MAXSTRINGLEN);
>-  strlcat (THIS->__retvalue, "one", MAXSTRINGLEN);
>+  strlcpy (THIS\->__retvalue, THIS\->val, MAXSTRINGLEN);
>+  strlcat (THIS\->__retvalue, "one", MAXSTRINGLEN);
> %}
> .ESAMPLE
> The function argument and return value types have to be inferred by
>@@ -640,9 +640,9 @@
> option),
> in order to allow more kernel-version-specific scripts to override less
> specific ones.  For example, for a kernel version
>-.IR 2.6.12-23.FC3
>+.IR 2.6.12\-23.FC3
> the following patterns would be searched, in sequence:
>-.IR 2.6.12-23.FC3/*.stp ,
>+.IR 2.6.12\-23.FC3/*.stp ,
> .IR 2.6.12/*.stp ,
> .IR 2.6/*.stp ,
> and finally
>@@ -748,7 +748,7 @@
> .PP
> The resource use limits are set by macros in the generated C code.
> These may be overridden with the
>-.R \-D
>+.BR \-D
> flag.  A selection of these is as follows: 
> .TP
> MAXNESTING
>@@ -804,7 +804,7 @@
> .TP
> /usr/lib/debug/lib/modules/VERSION
> The location of kernel debugging information when packaged into the
>-.IR kernel-debuginfo
>+.IR kernel\-debuginfo
> RPM.
> .TP
> /usr/libexec/systemtap/stpd
>diff -ruN src-old/stapex.5.in src/stapex.5.in
>--- src-old/stapex.5.in	2006-05-16 20:51:34.000000000 +0200
>+++ src/stapex.5.in	2006-07-22 16:57:28.000000000 +0200
>@@ -38,7 +38,7 @@
>   foreach (x+ in odds) {
>     log("odds[" . sprint(x) . "] = " . sprint(odds[x]))
>   }
>-  foreach (x in evens-) {
>+  foreach (x in evens\-) {
>     log("evens[" . sprint(x) . "] = " . sprint(evens[x]))
>   }
> }
>@@ -84,7 +84,7 @@
>   if (i < 1) error ("bad number")
>   if (i == 1) return 1
>   if (i == 2) return 2
>-  return fibonacci (i-1) + fibonacci (i-2)
>+  return fibonacci (i\-1) + fibonacci (i\-2)
> }
> probe begin {
>   log ("11th fibonacci number: " . sprint (fibonacci (11)))
>@@ -107,7 +107,7 @@
> option to the translator.  That output needs to be filtered because
> each inlined function instance is listed separately.
> .SAMPLE
>-% stap -p2 -e \[aq]probe kernel.function("*") {}\[aq] | sort | uniq
>+% stap \-p2 \-e \[aq]probe kernel.function("*") {}\[aq] | sort | uniq
> .ESAMPLE
> 
> 
>diff -ruN src-old/stapfuncs.5.in src/stapfuncs.5.in
>--- src-old/stapfuncs.5.in	2006-07-17 22:27:10.000000000 +0200
>+++ src/stapfuncs.5.in	2006-07-22 16:57:28.000000000 +0200
>@@ -10,7 +10,7 @@
> The signature line includes the name of the function, the type of
> its return value (if any), and the names and types of all parameters.
> The syntax is the same as printed with the 
>-.IR stap " option " -p2 .
>+.IR stap " option " \-p2 .
> Examples:
> 
> .TP
>diff -ruN src-old/stapprobes.5.in src/stapprobes.5.in
>--- src-old/stapprobes.5.in	2006-06-05 23:49:14.000000000 +0200
>+++ src/stapprobes.5.in	2006-07-22 16:57:28.000000000 +0200
>@@ -88,7 +88,7 @@
> .ESAMPLE
> The probe handler is run every N jiffies (a kernel-defined unit of
> time, typically between 1 and 60 ms).  If the "randomize" component is
>-given, a linearly distributed random value in the range [-M..+M] is
>+given, a linearly distributed random value in the range [\-M..+M] is
> added to N every time the handler is run.  N is restricted to a
> reasonable range (1 to around a million), and M is restricted to be
> smaller than N.  There are no target variables provided in either
>@@ -196,7 +196,7 @@
> .IR kernel_string " or " user_string
> functions.
> .TP
>-$var->field
>+$var\->field
> traversal to a structure's field.  The indirection operator
> may be repeated to follow more levels of pointers.
> .TP
>@@ -240,7 +240,7 @@
> shutdown.
> .TP
> timer.jiffies(1000).randomize(200)
>-refers to a periodic interrupt, every 1000 +/- 200 jiffies.
>+refers to a periodic interrupt, every 1000 +/\- 200 jiffies.
> .TP
> kernel.function("*init*"), kernel.function("*exit*")
> refers to all kernel functions with "init" or "exit" in the name.

Actions: View | Diff

Attachments on bug 3094: 1234