ADDR_TO_NODE

BEGIN/END/ERROR: +
NEVER: +
SYSCALL: +
TIMERS: +
DWARF: +
DWARFLESS: +
USER-SPACE: +
PROCFS: +
MARKERS: +
TRACEPOINTS: +
PERFORMANCE MONITORING HARDWARE: +

+This document was created by +man2html, +using the manual pages.
+Time: 19:56:13 GMT, September 28, 2009 + + diff --git a/man/stapprobes.3stap~.html b/man/stapprobes.3stap~.html new file mode 100644 index 00000000..8b9792e6 --- /dev/null +++ b/man/stapprobes.3stap~.html @@ -0,0 +1,1065 @@ + +Manpage of STAPPROBES + +

STAPPROBES

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

+ + +

NAME

+ +stapprobes - systemtap probe points +

+ + + +

+ +

DESCRIPTION

+ +The following sections enumerate the variety of probe points supported +by the systemtap translator, and additional aliases defined by +standard tapset scripts. +

+ +
+ +

+kernel.function("foo").return
+process("/bin/vi").statement(0x2222)
+end
+syscall.*
+kernel.function("no_such_function") ?
+module("awol").function("no_such_function") !
+signal.*? if (switch)
+kprobe.function("foo")
+
+

+ +

+ + +

+ +

BEGIN/END/ERROR

+ +

+ +If the order of execution among "begin" or "end" probes is significant, +then an optional sequence number may be provided: +

+ +
+ +

+begin(N)
+end(N)
+
+

+ +

+ + +

+ +

NEVER

+ +

SYSCALL

+ +

+The +syscall.* + +aliases define several hundred probes, too many to +summarize here. They are: +

+ +
+ +

+syscall.NAME
+

+syscall.NAME.return
+
+

+ +

+ + +

argstr + +: +A pretty-printed form of the entire argument list, without parentheses. +
name + +: +The name of the system call. +
retstr + +: +For return probes, a pretty-printed form of the system-call result. +

+ +Not all probe aliases obey all of these general guidelines. Please report +any bothersome ones you encounter as a bug. +

+ +

TIMERS

+ +

+Intervals defined by the standard kernel "jiffies" timer may be used +to trigger probe handlers asynchronously. Two probe point variants +are supported by the translator: +

+ +
+ +

+timer.jiffies(N)
+timer.jiffies(N).randomize(M)
+
+

+ +

+ + +

+ +Alternatively, intervals may be specified in units of time. +There are two probe point variants similar to the jiffies timer: +

+ +
+ +

+timer.ms(N)
+timer.ms(N).randomize(M)
+
+

+ +

+ + +

+ +Profiling timers are also available to provide probes that execute on all +CPUs at the rate of the system tick (CONFIG_HZ). +This probe takes no parameters. +

+ +
+ +

+timer.profile
+
+

+ +

+ + +

+Full context information of the interrupted process is available, making +this probe suitable for a time-based sampling profiler. +

+ +

DWARF

+ +

+ +Points in a kernel, which are identified by +module, source file, line number, function name, or some +combination of these. +

+ +
+ +

+kernel.function(PATTERN)
+

+kernel.function(PATTERN).call
+

+kernel.function(PATTERN).return
+

+kernel.function(PATTERN).inline
+

+kernel.function(PATTERN).label(LPATTERN)
+

+module(MPATTERN).function(PATTERN)
+

+module(MPATTERN).function(PATTERN).call
+

+module(MPATTERN).function(PATTERN).return
+

+module(MPATTERN).function(PATTERN).inline
+

+

+kernel.statement(PATTERN)
+

+kernel.statement(ADDRESS).absolute
+

+module(MPATTERN).statement(PATTERN)
+
+

+ +

+ + +

*: +The first part is the name of a function, as would appear in the +nm + +program's output. This part may use the "*" and "?" wildcarding +operators to match multiple names. +
*: +The second part is optional and begins with the "@" character. +It is followed by the path to the source file containing the function, +which may include a wildcard pattern, such as mm/slab*. +If it does not match as is, an implicit "*/" is optionally added +before + +the pattern, so that a script need only name the last few components +of a possibly long source directory path. +
*: +Finally, the third part is optional if the file name part was given, +and identifies the line number in the source file preceded by a ":" +or a "+". The line number is assumed to be an +absolute line number if preceded by a ":", or relative to the entry of +the function if preceded by a "+". +All the lines in the function can be matched with ":*". +A range of lines x through y can be matched with ":x-y". +

$var: +refers to an in-scope variable "var". If it's an integer-like type, +it will be cast to a 64-bit int for systemtap script use. String-like +pointers (char *) may be copied to systemtap string values using the +kernel_string or user_string + +functions. +
$var->field: +traversal to a structure's field. The indirection operator +may be repeated to follow more levels of pointers. +
$return: +is available in return probes only for functions that are declared +with a return value. +

$var[N]: +; +indexes into an array. The index is given with a +literal number. +
$$vars: +expands to a character string that is equivalent to +sprintf("parm1=%x ... parmN=%x var1=%x ... varN=%x", parm1, ..., parmN, +var1, ..., varN) +
$$locals: +expands to a subset of $$vars for only local variables. +
$$parms: +expands to a subset of $$vars for only function parameters. +
$$return: +is available in return probes only. It expands to a string that +is equivalent to sprintf("return=%x", $return) +if the probed function has a return value, or else an empty string. +

+ +

DWARFLESS

+kprobe.function(FUNCTION)
+kprobe.function(FUNCTION).return
+kprobe.module(NAME).function(FUNCTION)
+kprobe.module(NAME).function(FUNCTION).return
+kprobe.statement.(ADDRESS).absolute
+
+

+ +

+ + +

+ +Note that +FUNCTION + +and +MODULE + +names +must not + +contain wildcards, or the probe will not be registered. +Also, statement probes must be run under guru-mode only. +

+ +

USER-SPACE

+ +Support for user-space probing is available for kernels +that are configured with the utrace extensions. See + +
+ +

+http://people.redhat.com/roland/utrace/
+
+

+ +

+ + +

+ +There are several forms. First, a non-symbolic probe point: + +
+ +

+process(PID).statement(ADDRESS).absolute
+
+

+ +

+ +Second, non-symbolic user-kernel interface events handled by +utrace may be probed: + +
+ +

+process(PID).begin
+process("PATH").begin
+process.begin
+process(PID).thread.begin
+process("PATH").thread.begin
+process.thread.begin
+process(PID).end
+process("PATH").end
+process.end
+process(PID).thread.end
+process("PATH").thread.end
+process.thread.end
+process(PID).syscall
+process("PATH").syscall
+process.syscall
+process(PID).syscall.return
+process("PATH").syscall.return
+process.syscall.return
+process(PID).insn
+process("PATH").insn
+process(PID).insn.block
+process("PATH").insn.block
+
+

+ +

+ + +

+ +Third, symbolic static instrumentation compiled into programs and +shared libraries may be +probed: + +
+ +

+process("PATH").mark("LABEL")
+
+

+ +

+ + +

+process("PATH").function("NAME")
+process("PATH").statement("*@FILE.c:123")
+process("PATH").function("*").return
+process("PATH").function("myfun").label("foo")
+
+

+ +

+ + +

+ +

PROCFS

+ +

+ +
+ +

+procfs("PATH").read
+procfs("PATH").write
+procfs.read
+procfs.write
+
+

+ +

+ + +

+PATH + +is the file name (relative to /proc/systemtap/MODNAME) to be created. +If no +PATH + +is specified (as in the last two variants above), +PATH + +defaults to "command". +

+ +
+ +

+procfs("PATH").read { $value = "100\n" }
+
+

+ +

+ + +

+ +
+ +

+procfs("PATH").write { printf("user wrote: %s", $value) }
+
+

+ +

+ + +

+ +

MARKERS

+ +

+The marker format string associated with a marker is available in +$format. + +And also the marker name string is available in +$name. + +

+ +

TRACEPOINTS

+ +

+The name of the tracepoint is available in +$$name, + +and a string of name=value pairs for all parameters of the tracepoint +is available in +$$vars or $$parms. + +

+ +

PERFORMANCE MONITORING HARDWARE

+ +

+ +
+ +

+pfmon -l
+
+

+ +

+ + +

$counter: +is a handle used in the body of the probe for operations +involving the counter associated with the probe. +
read_counter: +is a function that is passed the handle for the perfmon probe and returns +the current count for the event. +
+

+ +

EXAMPLES

+ +

+ +Here are some example probe points, defining the associated events. +

begin, end, end: +refers to the startup and normal shutdown of the session. In this +case, the handler would run once during startup and twice during +shutdown. +
timer.jiffies(1000).randomize(200): +refers to a periodic interrupt, every 1000 +/- 200 jiffies. +
kernel.function("*init*"), kernel.function("*exit*"): +refers to all kernel functions with "init" or "exit" in the name. +
kernel.function("*@kernel/sched.c:240"): +refers to any functions within the "kernel/sched.c" file that span +line 240. +
kernel.mark("getuid"): +refers to an STAP_MARK(getuid, ...) macro call in the kernel. +
module("usb*").function("*sync*").return: +refers to the moment of return from all functions with "sync" in the +name in any of the USB drivers. +
kernel.statement(0xc0044852): +refers to the first byte of the statement whose compiled instructions +include the given address in the kernel. +
kernel.statement("*@kernel/sched.c:2917"): +refers to the statement of line 2917 within "kernel/sched.c". +
kernel.statement("bio_init@fs/bio.c+3"): +refers to the statement at line bio_init+3 within "fs/bio.c". +
syscall.*.return: +refers to the group of probe aliases with any name in the third position +
+

+ +

Index

BEGIN/END/ERROR: +
NEVER: +
SYSCALL: +
TIMERS: +
DWARF: +
DWARFLESS: +
USER-SPACE: +
PROCFS: +
MARKERS: +
TRACEPOINTS: +
PERFORMANCE MONITORING HARDWARE: +

+This document was created by +man2html, +using the manual pages.
+Time: 19:56:13 GMT, September 28, 2009 + + diff --git a/man/stapprobes.5.html b/man/stapprobes.5.html deleted file mode 100644 index bb146f98..00000000 --- a/man/stapprobes.5.html +++ /dev/null @@ -1,610 +0,0 @@ - -Manpage of STAPPROBES - -

STAPPROBES

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

- - -

NAME

- -stapprobes - systemtap probe points -

- - - -

- -

DESCRIPTION

- -The following sections enumerate the variety of probe points supported -by the systemtap translator, and additional aliases defined by -standard tapset scripts. -

- -The general probe point syntax is a dotted-symbol sequence. This -allows a breakdown of the event namespace into parts, somewhat like -the Domain Name System does on the Internet. Each component -identifier may be parametrized by a string or number literal, with a -syntax like a function call. A component may include a "*" -character, to expand to other matching probe points. A probe point -may be followed by a "?" character, to indicate that it is optional, -and that no error should result if it fails to expand. Optionalness -passes down through all levels of alias/wildcard expansion. -

-These are all syntactically valid probe points: -

- -
- -

-kernel.function("foo").return
-syscall(22)
-user.inode("/bin/vi").statement(0x2222)
-end
-syscall.*
-kernel.function("no_such_function") ?
-
-

- -

- - -

-Probes may be broadly classified into "synchronous" and -"asynchronous". A "synchronous" event is deemed to occur when any -processor executes an instruction matched by the specification. This -gives these probes a reference point (instruction address) from which -more contextual data may be available. Other families of probe points -refer to "asynchronous" events such as timers/counters rolling over, -where there is no fixed reference point that is related. Each probe -point specification may match multiple locations (for example, using -wildcards or aliases), and all them are then probed. A probe -declaration may also contain several comma-separated specifications, -all of which are probed. -

- -

BEGIN/END/ERROR

- -

-The probe points -begin and end - -are defined by the translator to refer to the time of session startup -and shutdown. All "begin" probe handlers are run, in some sequence, -during the startup of the session. All global variables will have -been initialized prior to this point. All "end" probes are run, in -some sequence, during the -normal - -shutdown of a session, such as in the aftermath of an -exit () - -function call, or an interruption from the user. In the case of an -error-triggered shutdown, "end" probes are not run. There are no -target variables available in either context. -

- -If the order of execution among "begin" or "end" probes is significant, -then an optional sequence number may be provided: -

- -
- -

-begin(N)
-end(N)
-
-

- -

- - -

-The number N may be positive or negative. The probe handlers are run in -increasing order, and the order between handlers with the same sequence -number is unspecified. When "begin" or "end" are given without a -sequence, they are effectively sequence zero. -

-The -error - -probe point is similar to the -end - -probe, except that each such probe handler run when the session and -after errors having occurred. In such cases, "end" probes are -skipped, but each "error" prober is still attempted. This kind of -probe can be used to clean up or emit a final gasp message. It may -also be numerically parametrized to set a sequence. -

- -

NEVER

- -The probe point -never - -is specially defined by the translator to mean "never". Its probe -handler is never run, though its statements are analyzed for symbol / -type correctness as usual. This probe point may be useful in -conjunction with optional probes. -

- -

TIMERS

- -

-Intervals defined by the standard kernel "jiffies" timer may be used -to trigger probe handlers asynchronously. Two probe point variants -are supported by the translator: -

- -
- -

-timer.jiffies(N)
-timer.jiffies(N).randomize(M)
-
-

- -

- - -

-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 -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 -context. It is possible for such probes to be run concurrently on -a multi-processor computer. -

- -Alternatively, intervals may be specified in units of time. -There are two probe point variants similar to the jiffies timer: -

- -
- -

-timer.ms(N)
-timer.ms(N).randomize(M)
-
-

- -

- - -

-Here, N and M are specified in milliseconds, but the full options for units -are seconds (s/sec), milliseconds (ms/msec), microseconds (us/usec), -nanoseconds (ns/nsec), and hertz (hz). Randomization is not supported for -hertz timers. -

-The actual resolution of the timers depends on the target kernel. For -kernels prior to 2.6.17, timers are limited to jiffies resolution, so -intervals are rounded up to the nearest jiffies interval. After 2.6.17, -the implementation uses hrtimers for tighter precision, though the actual -resolution will be arch-dependent. In either case, if the "randomize" -component is given, then the random value will be added to the interval -before any rounding occurs. -

- -Profiling timers are also available to provide probes that execute on all -CPUs at the rate of the system tick. This probe takes no parameters. -

- -
- -

-timer.profile
-
-

- -

- - -

-Full context information of the interrupted process is available, making -this probe suitable for a time-based sampling profiler. -

- -

DWARF

- -

-This family of probe points uses symbolic debugging information for -the target kernel/module/program, as may be found in unstripped -executables, or the separate -debuginfo - -packages. They allow placement of probes logically into the execution -path of the target program, by specifying a set of points in the -source or object code. When a matching statement executes on any -processor, the probe handler is run in that context. -

- -Points in a kernel, which are identified by -module, source file, line number, function name, or some -combination of these. -

- -Here is a list of probe point families currently supported. The -.function - -variant places a probe near the beginning of the named function, so that -parameters are available as context variables. The -.return - -variant places a probe at the moment of return from the named function, so -the return value is available as the "$return" context variable. -The -.inline - -modifier for -.function - -filters the results to include only instances of inlined functions. -The -.call - -modifier selects the opposite subset. Inline functions do not have an -identifiable return point, so -.return - -is not supported on -.inline - -probes. The -.statement - -variant places a probe at the exact spot, exposing those local variables -that are visible there. -

- -
- -

-kernel.function(PATTERN)
-

-kernel.function(PATTERN).call
-

-kernel.function(PATTERN).return
-

-kernel.function(PATTERN).inline
-

-module(MPATTERN).function(PATTERN)
-

-module(MPATTERN).function(PATTERN).call
-

-module(MPATTERN).function(PATTERN).return
-

-module(MPATTERN).function(PATTERN).inline
-

-

-kernel.statement(PATTERN)
-

-kernel.statement(ADDRESS).absolute
-

-module(MPATTERN).statement(PATTERN)
-
-

- -

- - -

-In the above list, MPATTERN stands for a string literal that aims to -identify the loaded kernel module of interest. It may include "*", "[]", -and "?" wildcards. PATTERN stands for a string literal that -aims to identify a point in the program. It is made up of three -parts: -

*: -The first part is the name of a function, as would appear in the -nm - -program's output. This part may use the "*" and "?" wildcarding -operators to match multiple names. -
*: -The second part is optional and begins with the "@" character. -It is followed by the path to the source file containing the function, -which may include a wildcard pattern, such as mm/slab*. -In most cases, the path should be relative to the top of the -linux source directory, although an absolute path may be necessary for some kernels. -If a relative pathname doesn't work, try absolute. -
*: -Finally, the third part is optional if the file name part was given, -and identifies the line number in the source file, preceded by a ":". -

- -As an alternative, PATTERN may be a numeric constant, indicating an -(module-relative or kernel-_stext-relative) address. In guru mode -only, absolute kernel addresses may be specified with the ".absolute" -suffix. -

- -Some of the source-level variables, such as function parameters, -locals, globals visible in the compilation unit, may be visible to -probe handlers. They may refer to these variables by prefixing their -name with "$" within the scripts. In addition, a special syntax -allows limited traversal of structures, pointers, and arrays. -

$var: -refers to an in-scope variable "var". If it's an integer-like type, -it will be cast to a 64-bit int for systemtap script use. String-like -pointers (char *) may be copied to systemtap string values using the -kernel_string or user_string - -functions. -
$var->field: -traversal to a structure's field. The indirection operator -may be repeated to follow more levels of pointers. -
$var[N]: -indexes into an array. The index is given with a -literal number. -
-

- -

PROCFS

- -

-These probe points allow procfs "files" in -/proc/systemtap/MODNAME to be created, read and written -(MODNAME - -is the name of the systemtap module). The -proc - -filesystem is a pseudo-filesystem which is used an an interface to -kernel data structures. There are four probe point variants supported -by the translator: -

- -
- -

-procfs("PATH").read
-procfs("PATH").write
-procfs.read
-procfs.write
-
-

- -

- - -

-PATH - -is the file name (relative to /proc/systemtap/MODNAME) to be created. -If no -PATH - -is specified (as in the last two variants above), -PATH - -defaults to "command". -

- -When a user reads /proc/systemtap/MODNAME/PATH, the corresponding -procfs -read - -probe is triggered. The string data to be read should be assigned to -a variable named -$value, - -like this: -

- -
- -

-procfs("PATH").read { $value = "100\n" }
-
-

- -

- - -

- -When a user writes into /proc/systemtap/MODNAME/PATH, the -corresponding procfs -write - -probe is triggered. The data the user wrote is available in the -string variable named -$value, - -like this: -

- -
- -

-procfs("PATH").write { printf("user wrote: %s", $value) }
-
-

- -

- - -

- -

MARKERS

- -

-This family of probe points hooks up to static probing markers -inserted into the kernel or modules. These markers are special macro -calls inserted by kernel developers to make probing faster and more -reliable than with DWARF-based probes. Further, DWARF debugging -information is -not - -required to probe markers. -

-Marker probe points begin with -kernel or module(name), - -just like DWARF probes. This identifies the source of symbol table -used for finding markers. The next part names the marker itself: -mark(name). - -The marker name string, which may contain the usual wildcard characters, -is matched against the names given to the marker macros when the kernel -or module was compiled. -

-The handler associated with a marker-based probe may read the -optional parameters specified at the macro call site. These are -named -$arg1 through $argNN, - -where NN is the number of parameters supplied by the macro. Number -and string parameters are passed in a type-safe manner. -

- -

PERFORMANCE MONITORING HARDWARE

- -

-The perfmon family of probe points is used to access the performance -monitoring hardware available in modern processors. This family of -probes points needs the perfmon2 support in the kernel to access the -performance monitoring hardware. -

- -Performance monitor hardware points begin with a -perfmon. - -The next part of the names the event being counted -counter(event). - -The event names are processor implementation specific with the -execption of the generic -cycles and instructions - -events, which are available on all processors. This sets up a counter -on the processor to count the number of events occuring on the -processor. For more details on the performance monitoring events -available on a specific processor use the command perfmon2 command: -

- -
- -

-pfmon -l
-
-

- -

- - -

$counter: -is a handle used in the body of the probe for operations -involving the counter associated with the probe. -
read_counter: -is a function that is passed the handle for the perfmon probe and returns -the current count for the event. -
-

- -

EXAMPLES

- -

- -Here are some example probe points, defining the associated events. -

begin, end, end: -refers to the startup and normal shutdown of the session. In this -case, the handler would run once during startup and twice during -shutdown. -
timer.jiffies(1000).randomize(200): -refers to a periodic interrupt, every 1000 +/- 200 jiffies. -
kernel.function("*init*"), kernel.function("*exit*"): -refers to all kernel functions with "init" or "exit" in the name. -
kernel.function("*@kernel/sched.c:240"): -refers to any functions within the "kernel/sched.c" file that span -line 240. -
kernel.mark("getuid"): -refers to an STAP_MARK(getuid, ...) macro call in the kernel. -
module("usb*").function("*sync*").return: -refers to the moment of return from all functions with "sync" in the -name in any of the USB drivers. -
kernel.statement(0xc0044852): -refers to the first byte of the statement whose compiled instructions -include the given address in the kernel. -
kernel.statement("*@kernel/sched.c:2917"): -refers to the statement of line 2917 within the "kernel/sched.c". -
syscall.*.return: -refers to the group of probe aliases with any name in the third position -
-

- -

Index

BEGIN/END/ERROR: -
NEVER: -
TIMERS: -
DWARF: -
PROCFS: -
MARKERS: -
PERFORMANCE MONITORING HARDWARE: -

-This document was created by -man2html, -using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 - - diff --git a/man/stapprobes.iosched.5.html b/man/stapprobes.iosched.3stap.html similarity index 90% rename from man/stapprobes.iosched.5.html rename to man/stapprobes.iosched.3stap.html index 538888d7..35f92d38 100644 --- a/man/stapprobes.iosched.5.html +++ b/man/stapprobes.iosched.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.IOSCHED

STAPPROBES.IOSCHED

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -124,7 +124,7 @@ Fires when a request is completed stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -140,6 +140,6 @@ Fires when a request is completed This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.process.5.html b/man/stapprobes.kprocess.3stap.html similarity index 73% rename from man/stapprobes.process.5.html rename to man/stapprobes.kprocess.3stap.html index 9dde5359..7742db80 100644 --- a/man/stapprobes.process.5.html +++ b/man/stapprobes.kprocess.3stap.html @@ -1,14 +1,14 @@ -Manpage of STAPPROBES.PROCESS +Manpage of STAPPROBES.KPROCESS -

STAPPROBES.PROCESS

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

STAPPROBES.KPROCESS

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

-stapprobes.process - systemtap process probe points +stapprobes.kprocess - systemtap kernel process probe points

@@ -18,12 +18,12 @@ stapprobes.process - systemtap process probe points

DESCRIPTION

-This family of probe points is used to probe the process activities. +This family of probe points is used to probe the kernel's process activities. It contains the following probe points:

process.create +

kprocess.create

@@ -42,7 +42,7 @@ result of one of the fork syscall variants, or a new kernel thread.
pid of the newly created process

process.start +

kprocess.start

@@ -55,7 +55,7 @@ Fires immediately before a new process begins execution.

process.exec +

kprocess.exec

@@ -69,7 +69,7 @@ Fires whenever a process attempts to exec to a new program
the path to the new executable

process.exec_complete +

kprocess.exec_complete

@@ -87,12 +87,12 @@ Fires at the completion of an exec call
a boolean indicating whether the exec was successful

process.exit +

kprocess.exit

Fires when a process terminates. This will always be followed by a -process.release, though the latter may be delayed if the process +kprocess.release, though the latter may be delayed if the process waits in a zombie state.

Arguments: @@ -103,12 +103,12 @@ waits in a zombie state.
the exit code of the process

process.release +

kprocess.release

Fires when a process is released from the kernel. This always -follows a process.exit, though it may be delayed somewhat if the +follows a kprocess.exit, though it may be delayed somewhat if the process waits in a zombie state.

Arguments: @@ -128,7 +128,7 @@ process waits in a zombie state. stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -144,6 +144,6 @@ process waits in a zombie state. This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.netdev.5.html b/man/stapprobes.netdev.3stap.html similarity index 88% rename from man/stapprobes.netdev.5.html rename to man/stapprobes.netdev.3stap.html index 51fc17e5..2208e9c4 100644 --- a/man/stapprobes.netdev.5.html +++ b/man/stapprobes.netdev.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.NETDEV

STAPPROBES.NETDEV

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -83,7 +83,7 @@ Fires when the network device wants to transmit a buffer

truesize -
The size of the the data to be transmitted. +
The size of the data to be transmitted.

@@ -91,7 +91,7 @@ Fires when the network device wants to transmit a buffer stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -106,6 +106,6 @@ Fires when the network device wants to transmit a buffer This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.nfs.5.html b/man/stapprobes.nfs.3stap.html similarity index 95% rename from man/stapprobes.nfs.5.html rename to man/stapprobes.nfs.3stap.html index 25370ec3..f461af46 100644 --- a/man/stapprobes.nfs.5.html +++ b/man/stapprobes.nfs.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.NFS

STAPPROBES.NFS

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -705,7 +705,7 @@ Fires when a previous async read operation failed

-Fies when in readahead way,read several pages once +Fires when in readahead way, read several pages once

Arguments: @@ -739,7 +739,7 @@ Fies when in readahead way,read several pages once

-Fies whenever a nfs read pages operation is done +Fires whenever a nfs read pages operation is done

Arguments: @@ -753,7 +753,7 @@ Fies whenever a nfs read pages operation is done

-Fies whenever set page dirty on nfs client side +Fires whenever set page dirty on nfs client side

Arguments: @@ -771,7 +771,7 @@ Fies whenever set page dirty on nfs client side

-Fies whenever writing an mapped page to the server from nfs client side +Fires whenever writing an mapped page to the server from nfs client side

Arguments: @@ -826,7 +826,7 @@ Fies whenever writing an mapped page to the server from nfs client side

-Fies whenever writing several dirty pages to the server from nfs client sides +Fires whenever writing several dirty pages to the server from nfs client sides

Arguments: @@ -865,7 +865,7 @@ Fies whenever writing several dirty pages to the server from nfs client sides

-Fies whenever prepare a page for writting on nfs client sides +Fires whenever prepare a page for writing on nfs client sides

Arguments: @@ -903,7 +903,7 @@ Fies whenever prepare a page for writting on nfs client sides

-Fies often after prepare write operation +Fires often after prepare write operation

Arguments: @@ -994,7 +994,7 @@ Fies often after prepare write operation

filename -
the name of file which client opens/searchs on server +
the name of file which client opens/searches on server

name_len @@ -1097,7 +1097,7 @@ Fires when client synchronously writes file to server

-Fires when synchronously writting file from server is done +Fires when synchronously writing file from server is done

Arguments: @@ -1111,7 +1111,7 @@ Fires when synchronously writting file from server is done

-Fires when client writes the buffered data to disk,the buffered +Fires when client writes the buffered data to disk, the buffered data is asynchronously written by client before(not exist in NFSV2)

Arguments: @@ -1162,7 +1162,7 @@ Fires when committing operation is done

Fires when client asynchronously reads file from server, -this function is used to setup a read rpc task,not do +this function is used to setup a read rpc task, not do a real read operation.

Arguments: @@ -1221,7 +1221,7 @@ Fires when a read reply is received or some read error occur

timestamp -
  time stamp ,which is used for lease renewal (only +
  time stamp, which is used for lease renewal (only
  in nfs.proc4.read_done)

@@ -1230,7 +1230,7 @@ Fires when a read reply is received or some read error occur

Fires when client asynchronously write data to server, -this function is used to setup a write rpc task,not do +this function is used to setup a write rpc task, not do a write read operation.

Arguments: @@ -1258,7 +1258,7 @@ a write read operation.

how -
  used to set args.stable,The possible value could be: +
  used to set args.stable, The possible value could be:
          NFS_UNSTABLE,
          NFS_DATA_SYNC,
          NFS_FILE_SYNC @@ -1298,7 +1298,7 @@ Fires when a write reply is received or some write error occur

valid -
fattr->valid ,indicates which fields are valid +
fattr->valid, indicates which fields are valid

count @@ -1306,7 +1306,7 @@ Fires when a write reply is received or some write error occur

timestamp -
  time stamp ,which is used for lease renewal (only +
  time stamp, which is used for lease renewal (only
  in nfs.proc4.read_done)

@@ -1315,7 +1315,7 @@ Fires when a write reply is received or some write error occur

Fires when client asynchronously do a commit operation, -this function is used to setup a commit rpc task,not do +this function is used to setup a commit rpc task, not do a commit read operation.

Arguments: @@ -1375,7 +1375,7 @@ Fires when a commit reply is received or some commit error occur

valid -
fattr->valid ,indicates which fields are valid +
fattr->valid, indicates which fields are valid

count @@ -1383,7 +1383,7 @@ Fires when a commit reply is received or some commit error occur

timestamp -
  time stamp ,which is used for lease renewal (only +
  time stamp, which is used for lease renewal (only
  in nfs.proc4.read_done)

@@ -1591,7 +1591,7 @@ Fires whenever nfs client renames a file on server stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -1607,6 +1607,6 @@ Fires whenever nfs client renames a file on server This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.nfsd.5.html b/man/stapprobes.nfsd.3stap.html similarity index 92% rename from man/stapprobes.nfsd.5.html rename to man/stapprobes.nfsd.3stap.html index dab75715..d0baeadf 100644 --- a/man/stapprobes.nfsd.5.html +++ b/man/stapprobes.nfsd.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.NFSD

STAPPROBES.NFSD

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -31,7 +31,7 @@ It contains the following probe points:

-Fires whenever client opens/searchs file on server +Fires whenever client opens/searches file on server

Arguments: @@ -96,7 +96,7 @@ Fires whenever client reads file on server

vec -
  struct kvec ,includes buf address in kernel address +
  struct kvec, includes buf address in kernel address
  and the length of each buffer

vlen @@ -139,7 +139,7 @@ Fires whenever client writes data to file on server

vec -
  struct kvec ,includes buf address in kernel address +
  struct kvec, includes buf address in kernel address
  and the length of each buffer

vlen @@ -378,7 +378,7 @@ Fires whenever server reads file

vec -
  struct kvec ,includes buf address in kernel address +
  struct kvec, includes buf address in kernel address
  and the length of each buffer

vlen @@ -413,7 +413,7 @@ Fires whenever server writes file

vec -
  struct kvec ,includes buf address in kernel address +
  struct kvec, includes buf address in kernel address
  and the length of each buffer

vlen @@ -447,7 +447,7 @@ Fires when server commits all pending writes to stable storage

-Fires whenever client opens/searchs file on server +Fires whenever client opens/searches file on server

Arguments: @@ -506,7 +506,7 @@ Fires whenever client opens/searchs file on server

Fires when client creates a regular file or set file attributes -on server side,only called by nfsd3_proc_create and nfsd4_open +on server side, only called by nfsd3_proc_create and nfsd4_open (op_claim_type is NFS4_OPEN_CLAIM_NULL)

Arguments: @@ -534,16 +534,16 @@ on server side,only called by nfsd3_proc_create and nfsd4_open

createmode -
  create mode .The possible values could be: +
  create mode. The possible values could be:
    NFS3_CREATE_EXCLUSIVE,NFS3_CREATE_UNCHECKED,NFS3_CREATE_GUARDED

truncp -
trunp arguments, indicates if the file shouldbe truncate +
trunp arguments, indicates if the file should be truncated

verfier -
  file attributes (atime,mtime,mode).It's used to reset file +
  file attributes (atime,mtime,mode). It's used to reset file
  attributes for CREATE_EXCLUSIVE

@@ -624,7 +624,7 @@ Fires whenever server closes file

-Fires whenever server receives NFS operation from client +Fires whenever server receives NFS operation from client

Arguments: @@ -659,7 +659,7 @@ Fires whenever server receives NFS operation from client stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -675,6 +675,6 @@ Fires whenever server receives NFS operation from client This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.pagefault.5.html b/man/stapprobes.pagefault.3stap.html similarity index 82% rename from man/stapprobes.pagefault.5.html rename to man/stapprobes.pagefault.3stap.html index 96e182d5..1f4e984d 100644 --- a/man/stapprobes.pagefault.5.html +++ b/man/stapprobes.pagefault.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.PAGEFAULT

STAPPROBES.PAGEFAULT

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -45,7 +45,7 @@ Fires when there is a pagefault stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -61,6 +61,6 @@ Fires when there is a pagefault This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.rpc.5.html b/man/stapprobes.rpc.3stap.html similarity index 98% rename from man/stapprobes.rpc.5.html rename to man/stapprobes.rpc.3stap.html index 0d6a953d..8bb6650a 100644 --- a/man/stapprobes.rpc.5.html +++ b/man/stapprobes.rpc.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.RPC

STAPPROBES.RPC

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -490,7 +490,7 @@ Fires when an RPC client is to be processed

rq_prot -
The IP protocol of the reqeust +
The IP protocol of the request

sunrpc.svc.authorise @@ -527,7 +527,7 @@ Fires when an RPC client is to be authorised

rq_prot -
The IP protocol of the reqeust +
The IP protocol of the request

sunrpc.svc.recv @@ -589,7 +589,7 @@ Fires when want to return reply to client

rq_prot -
The IP protocol of the reqeust +
The IP protocol of the request

sunrpc.svc.drop @@ -626,7 +626,7 @@ Fires when a request is to be dropped

rq_prot -
The IP protocol of the reqeust +
The IP protocol of the request

sunrpc.sched.new_task @@ -762,7 +762,7 @@ Fires when a task is to be delayed stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -778,6 +778,6 @@ Fires when a task is to be delayed This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.scsi.5.html b/man/stapprobes.scsi.3stap.html similarity index 96% rename from man/stapprobes.scsi.5.html rename to man/stapprobes.scsi.3stap.html index 0238045c..be47f383 100644 --- a/man/stapprobes.scsi.5.html +++ b/man/stapprobes.scsi.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.SCSI

STAPPROBES.SCSI

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -184,7 +184,7 @@ block device I/O requests stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -200,6 +200,6 @@ block device I/O requests This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.signal.5.html b/man/stapprobes.signal.3stap.html similarity index 96% rename from man/stapprobes.signal.5.html rename to man/stapprobes.signal.3stap.html index 6559638e..6822184a 100644 --- a/man/stapprobes.signal.5.html +++ b/man/stapprobes.signal.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.SIGNAL

STAPPROBES.SIGNAL

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -90,7 +90,7 @@ Fires when return from sending a signal

-- return 0 if the signal is sucessfully sent to a process, +- return 0 if the signal is successfully sent to a process, which means the following:

<1> the signal is ignored by receiving process @@ -107,7 +107,7 @@ by user using something other than kill()
Return values for "send_group_sigqueue"

-- return 0 if the signal is either sucessfully added into the +- return 0 if the signal is either successfully added into the sigqueue of receiving process or a SI_TIMER entry is already queued so just increment the overrun count

@@ -118,7 +118,7 @@ queued so just increment the overrun count
Return values for "send_sigqueue"

@@ -229,8 +229,8 @@ Fires when wake up the process for new active signals

state_mask -
a string representation indicate the mask of task states -that can be woken. Possible values are +
a string representation indicate the mask of task states +that can be woken. Possible values are (TASK_INTERRUPTIBLE|TASK_STOPPED|TASK_TRACED) and TASK_INTERRUPTIBLE.

@@ -639,7 +639,7 @@ Fires when flush all pending signals for a task stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -655,6 +655,6 @@ Fires when flush all pending signals for a task This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.socket.5.html b/man/stapprobes.socket.3stap.html similarity index 97% rename from man/stapprobes.socket.5.html rename to man/stapprobes.socket.3stap.html index cf591d57..ab9a7e03 100644 --- a/man/stapprobes.socket.5.html +++ b/man/stapprobes.socket.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.SOCKET

STAPPROBES.SOCKET

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -62,7 +62,7 @@ The message sender.
to convert to a string.

    Common values include: -
         0 - IP (Internet Procotol, local interprocess communications) +
         0 - IP (Internet Protocol, local interprocess communications)
         6 - TCP (Transmission Control Protocol)
        17 - UDP (User Datagram Protocol)
       132 - SCTP (Stream Control Transmission Protocol) @@ -604,9 +604,9 @@ The socket closer. stap(1), -stapprobes(5), +stapprobes(3stap), -stapfuncs(5) +stapfuncs(3stap)

@@ -621,6 +621,6 @@ The socket closer. This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.tcp.5.html b/man/stapprobes.tcp.3stap.html similarity index 88% rename from man/stapprobes.tcp.5.html rename to man/stapprobes.tcp.3stap.html index a9e555b3..36accf43 100644 --- a/man/stapprobes.tcp.5.html +++ b/man/stapprobes.tcp.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.TCP

STAPPROBES.TCP

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -124,7 +124,7 @@ Fires when returning from tcp.disconnect stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -140,6 +140,6 @@ Fires when returning from tcp.disconnect This document was created by man2html, using the manual pages.
-Time: 22:28:06 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapprobes.udp.5.html b/man/stapprobes.udp.3stap.html similarity index 88% rename from man/stapprobes.udp.5.html rename to man/stapprobes.udp.3stap.html index 7bfd5756..cba87414 100644 --- a/man/stapprobes.udp.5.html +++ b/man/stapprobes.udp.3stap.html @@ -2,8 +2,8 @@ Manpage of STAPPROBES.UDP

STAPPROBES.UDP

-Section: File Formats (5)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -124,7 +124,7 @@ Fires when returning from udp.disconnect stap(1), -stapprobes(5), +stapprobes(3stap)

@@ -140,6 +140,6 @@ Fires when returning from udp.disconnect This document was created by man2html, using the manual pages.
-Time: 22:28:06 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/staprun.8.html b/man/staprun.8.html index 64e65d3d..34ed84dc 100644 --- a/man/staprun.8.html +++ b/man/staprun.8.html @@ -2,8 +2,8 @@ Manpage of STAPRUN

STAPRUN

-Section: Maintenance Commands (8)
Updated: 2007-10-18
Index -Return to Main Contents

+Section: Maintenance Commands (8)
Updated: 2009-09-28
Index +Return to Main Contents

NAME

@@ -50,7 +50,7 @@ transfer the resulting kernel module to a production machine that doesn't have any development tools or kernel debugging information installed.

-This manual corresponds to version ?. +This manual corresponds to version 1.0.

OPTIONS

@@ -81,13 +81,15 @@ The '_stp_target' variable will be set to PID.

Send output to FILE. If the module uses bulk mode, the output will -be in percpu files FILE_x where 'x' is the cpu number. +be in percpu files FILE_x(FILE_cpux in background and bulk mode) +where 'x' is the cpu number. This supports strftime(3) formats +for FILE.

-b BUFFER_SIZE

The systemtap module will specify a buffer size. Setting one here will override that value. The value should be -an integer between 1 and 64 which be assumed to be the +an integer between 1 and 4095 which be assumed to be the buffer size in MB. That value will be per-cpu if bulk mode is used.

-L @@ -101,6 +103,28 @@ option.

Attach to loaded systemtap module. +

-d + +

+Delete a module. Only detached or unused modules +the user has permission to access will be deleted. Use "*" +(quoted) to delete all unused modules. +

-D + +

+Run staprun in background as a daemon and show it's pid. +

-S size[,N] + +

+Sets the maximum size of output file and the maximum number of output files. +If the size of output file will exceed +size + +, systemtap switches output file to the next file. And if the number of +output files exceed +N + +, systemtap removes the oldest output file. You can omit the second argument.

@@ -125,7 +149,7 @@ module.

EXAMPLES

See the -stapex(5) +stapex(3stap) manual page for a collection of sample scripts.

@@ -142,8 +166,7 @@ to compile a script. The program will report the pathname to the resulting module.

- - $ stap -p4 -e 'probe begin { printf("Hello World!\n"); exit() }' + $ stap -p4 -e [aq]probe begin { printf("Hello World!\n"); exit() }[aq]
/home/user/.systemtap/cache/85/stap_8553d83f78c_265.ko @@ -155,7 +178,6 @@ Run with the pathname to the module as an argument.

- $ staprun /home/user/.systemtap/cache/85/stap_8553d83f78c_265.ko
@@ -181,7 +203,55 @@ To reattach to a kernel module, the -A option would be used. +

FILE SWITCHING BY SIGNAL

+ +After the +staprun + +launched the +stapio + +, users can command it to switch output file to next file when it +outputs to file(s) (running staprun with +-o + +option) by sending a +SIGUSR2 + +signal to the +stapio + +process. When it receives SIGUSR2, it will switch output file to +new file with suffix +.N + +where N is the sequential number. +For example, +

+ + $ staprun -o foo ... +

+ +outputs trace logs to +foo + +and if it receives +SIGUSR2 + +signal, it switches output to +foo.1 + +file. And receiving +SIGUSR2 + +again, it switches to +foo.2 + +file. +

SAFETY AND SECURITY

Systemtap is an administrative tool. It exposes kernel internal data @@ -204,9 +274,9 @@ Members of the group can use staprun -to insert systemtap modules (or attach to existing systemtap modules) that +to insert or remove systemtap modules (or attach to existing systemtap modules) that are located in the /lib/modules/VERSION/systemtap directory. - +

FILES

@@ -219,24 +289,24 @@ group can only install modules located in this directory. This directory should be owned by the root user and not be world writable. - +

BUGS

Use the Bugzilla link off of the project web page or our mailing list. -http://sources.redhat.com/systemtap/,<systemtap@sources.redhat.com>. +http://sources.redhat.com/systemtap/, <systemtap@sources.redhat.com>.

@@ -252,15 +322,16 @@ Use the Bugzilla link off of the project web page or our mailing list.

ARGUMENTS

MODULE DETACHING AND ATTACHING

SAFETY AND SECURITY

FILES

FILE SWITCHING BY SIGNAL

BUGS

SAFETY AND SECURITY

FILES

BUGS

This document was created by man2html, using the manual pages.
-Time: 22:28:05 GMT, October 18, 2007 +Time: 19:56:13 GMT, September 28, 2009 diff --git a/man/stapvars.3stap.html b/man/stapvars.3stap.html new file mode 100644 index 00000000..8bc89f78 --- /dev/null +++ b/man/stapvars.3stap.html @@ -0,0 +1,93 @@ + +Manpage of STAPVARS + +

STAPVARS

+Section: Misc. Reference Manual Pages (3stap)
Updated: 2009-09-28
Index +Return to Main Contents

+ + +

NAME

+ +stapvars - systemtap variables +

+ +

DESCRIPTION

+ +The following sections enumerate the public variables provided by +standard tapsets installed under /home/fche/Private/DEVEL/DEVEL-systemtap/git/BUILD3/../INST3/share/systemtap/tapset. Each +variable is described with a type, and its behavior/restrictions. +The syntax is the same as printed with the +stap option -p2. + +Examples: +

example1:long: +Variable "example1" contains an integer. +
+
example2:string [long]: +Variable "example2" is an array of strings, indexed by integers. +
+

+ +

ARGV

+ +

argc:long: +Contains the value of the +$# + +value: the number of command line arguments passed to the systemtap script. +It is initialized with an implicit begin(-1) probe. +
+
argv:string [long]: +Contains each command line argument as a string. argv[1] will equal @1 if +there was at least one command line argument. Arguments beyond #32 are not +transcribed, and produce a warning message within the begin(-1) probe that +initializes this array. +
+

+ +

NULL

+ +

NULL:long: +Simply defined as the number 0. +
+

+ +

FILES

+ + +/home/fche/Private/DEVEL/DEVEL-systemtap/git/BUILD3/../INST3/share/systemtap/tapset + + +

+ +

Index

ARGV: +
NULL: +

FILES