From 4ea5a9d947ac41fc9da143ce501642673d27c7bf Mon Sep 17 00:00:00 2001 From: ddomingo Date: Mon, 1 Dec 2008 14:11:33 +1000 Subject: added index tags --- .../en-US/Array-Operations.xml | 8 +- doc/SystemTap_Beginners_Guide/en-US/Errors.xml | 530 ++++++++++++++++++++- 2 files changed, 529 insertions(+), 9 deletions(-) (limited to 'doc/SystemTap_Beginners_Guide') diff --git a/doc/SystemTap_Beginners_Guide/en-US/Array-Operations.xml b/doc/SystemTap_Beginners_Guide/en-US/Array-Operations.xml index b2f0df1b..c053c329 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Array-Operations.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Array-Operations.xml @@ -816,23 +816,23 @@ probe timer.s(2) array operations computing for statistical aggregates -adding values to statistical aggregatest +adding values to statistical aggregates operations computing for statistical aggregates -adding values to statistical aggregatest +adding values to statistical aggregates computing for statistical aggregates array operations -adding values to statistical aggregatest +adding values to statistical aggregates -adding values to statistical aggregatest +adding values to statistical aggregates computing for statistical aggregates array operations diff --git a/doc/SystemTap_Beginners_Guide/en-US/Errors.xml b/doc/SystemTap_Beginners_Guide/en-US/Errors.xml index f88d7c93..3f89ce0c 100644 --- a/doc/SystemTap_Beginners_Guide/en-US/Errors.xml +++ b/doc/SystemTap_Beginners_Guide/en-US/Errors.xml @@ -11,7 +11,20 @@
Parse and Semantic Errors - + +understanding SystemTap errors +parse/semantics error + + + +errors +parse/semantics error + + + +parse/semantics error +understanding SystemTap errors + These types of errors occur while SystemTap attempts to parse and translate the script into C, prior to being converted into a kernel module. For example type errors result from operations that assign invalid @@ -19,7 +32,67 @@ parse error: expected <replaceable>foo</replaceable>, saw <replaceable>bar</replaceable> - + + +understanding SystemTap errors +parse/semantics error +invalid values to variables/arrays + + + +errors +parse/semantics error +invalid values to variables/arrays + + + +parse/semantics error +understanding SystemTap errors +invalid values to variables/arrays + + + +invalid values to variables/arrays +parse/semantics error +understanding SystemTap errors + + + + + + + +understanding SystemTap errors +parse/semantics error +grammatical/typographical script error + + + +errors +parse/semantics error +grammatical/typographical script error + + + +parse/semantics error +understanding SystemTap errors +grammatical/typographical script error + + + + grammatical/typographical script error +parse/semantics error +understanding SystemTap errors + + + + +typographical script error +parse/semantics error +understanding SystemTap errors + + + The script contains a grammatical/typographical error. SystemTap detected type of construct that is incorrect, given the context of the probe. @@ -52,6 +125,43 @@ parse error: expected one of '. , ( ? ! { = +=' parse error: embedded code in unprivileged script + + + +understanding SystemTap errors +parse/semantics error +embedded code in unprivileged script + + + +errors +parse/semantics error +embedded code in unprivileged script + + + +parse/semantics error +understanding SystemTap errors +embedded code in unprivileged script + + + +embedded code in unprivileged script +parse/semantics error +understanding SystemTap errors + + + +unprivileged script, embedded code in +parse/semantics error +understanding SystemTap errors + + + +unsafe embedded code in unprivileged script +parse/semantics error +understanding SystemTap errors + The script contains unsafe embedded C code (blocks of code @@ -62,6 +172,34 @@ parse error: expected one of '. , ( ? ! { = +=' appear in the script. + + + + + +understanding SystemTap errors +parse/semantics error +guru mode + + + +errors +parse/semantics error +guru mode + + + +parse/semantics error +understanding SystemTap errors +guru mode + + + +guru mode +parse/semantics error +understanding SystemTap errors + + If you are sure of the safety of any similar constructs in the script and @@ -72,7 +210,37 @@ parse error: expected one of '. , ( ? ! { = +=' semantic error: type mismatch for identifier '<replaceable>foo</replaceable>' ... string vs. long - + + + +understanding SystemTap errors +parse/semantics error +type mismatch for identifier + + + +errors +parse/semantics error +type mismatch for identifier + + + +parse/semantics error +understanding SystemTap errors +type mismatch for identifier + + + +type mismatch for identifier +parse/semantics error +understanding SystemTap errors + + + +identifier type mismatch +parse/semantics error +understanding SystemTap errors + The function foo in the script used the wrong type @@ -95,14 +263,65 @@ probe syscall.open semantic error: unresolved type for identifier '<replaceable>foo</replaceable>' + + + +understanding SystemTap errors +parse/semantics error +unresolved type for identifier + + + +errors +parse/semantics error +unresolved type for identifier + + + +parse/semantics error +understanding SystemTap errors +unresolved type for identifier + + + +unresolved type for identifier +parse/semantics error +understanding SystemTap errors + The identifier (e.g. a variable) was used, but no type (integer or - string)could be determine. This occurs, for instance, if you use a + string) could be determined. This occurs, for instance, if you use a variable in a printf statement while no other function in the script can assign a value to it. semantic error: Expecting symbol or array index expression + + + +understanding SystemTap errors +parse/semantics error +expected symbol/array index expression + + + +errors +parse/semantics error +expected symbol/array index expression + + + +parse/semantics error +understanding SystemTap errors +expected symbol/array index expression + + + +expected symbol/array index expression +parse/semantics error +understanding SystemTap errors + + SystemTap could not assign a value to a variable or to a location in an array. The destination for the assignment is not a valid destination. @@ -117,6 +336,37 @@ probe syscall.open while searching for arity <replaceable>N</replaceable> function, semantic error: unresolved function call + + + +understanding SystemTap errors +parse/semantics error +unresolved function call + + + +errors +parse/semantics error +unresolved function call + + + +parse/semantics error +understanding SystemTap errors +unresolved function call + + + +unresolved function call +parse/semantics error +understanding SystemTap errors + + + +function call (unresolved) +parse/semantics error +understanding SystemTap errors + A function call or array index expression in the script used an invalid number of arguments/parameters. In SystemTap arity can either refer to the number of indices @@ -125,6 +375,36 @@ probe syscall.open semantic error: array locals not supported: + + + +array locals not supported +parse/semantics error +understanding SystemTap errors + + +understanding SystemTap errors +parse/semantics error +non-global arrays + + + +errors +parse/semantics error +non-global arrays + + + +parse/semantics error +understanding SystemTap errors +non-global arrays + + + +non-global arrays +parse/semantics error +understanding SystemTap errors + The script used an array operation without declaring the array as a global variable (global variables can be declared after their use in Systemtap scripts). Similar messages appear if an array is used, but with inconsistent arities. @@ -132,11 +412,63 @@ probe syscall.open semantic error: variable ’<replaceable>foo</replaceable>’ modified during ’foreach’ + + + +understanding SystemTap errors +parse/semantics error +variable modified during 'foreach' + + + +errors +parse/semantics error +variable modified during 'foreach' + + + +parse/semantics error +understanding SystemTap errors +variable modified during 'foreach' + + + +variable modified during 'foreach' +parse/semantics error +understanding SystemTap errors + The array foo is being modifed (being assigned to or deleted from) within an active foreach loop. This error also displays if an operation within the script performs a function call within the foreach loop. semantic error: probe point mismatch at position <replaceable>N</replaceable>, while resolving probe point <replaceable>foo</replaceable> + + + + + +understanding SystemTap errors +parse/semantics error +probe mismatch + + + +errors +parse/semantics error +probe mismatch + + + +parse/semantics error +understanding SystemTap errors +probe mismatch + + + +probe mismatch +parse/semantics error +understanding SystemTap errors + SystemTap did not understand what the event or SystemTap function foo refers to. This usually means that SystemTap could not find a match for @@ -149,16 +481,106 @@ probe syscall.open semantic error: no match for probe point, while resolving probe point <replaceable>foo</replaceable> + + + + + +understanding SystemTap errors +parse/semantics error +no match for probe point + + + +errors +parse/semantics error +no match for probe point + + + +parse/semantics error +understanding SystemTap errors +no match for probe point + + + +no match for probe point +parse/semantics error +understanding SystemTap errors + + + +probe point (no match for) +parse/semantics error +understanding SystemTap errors + The events / handler function foo could not be resolved altogether, for a variety of reasons. This error occurs when the script contains the event kernel.function("blah"), and blah does not exist. In some cases, the error could also mean the script contains an invalid kernel file name or source line number. semantic error: unresolved target-symbol expression + + + +understanding SystemTap errors +parse/semantics error +unresolved target-symbol expression + + + +errors +parse/semantics error +unresolved target-symbol expression + + + +parse/semantics error +understanding SystemTap errors +unresolved target-symbol expression + + + +unresolved target-symbol expression +parse/semantics error +understanding SystemTap errors + + + +target-symbol expression, unresolved +parse/semantics error +understanding SystemTap errors + A handler in the script references a target variable, but the value of the variable could not be resolved. This error could also mean that a handler is referencing a target variable that is not valid at all in the context when it was referenced. semantic error: libdwfl failure + + + + +understanding SystemTap errors +parse/semantics error +libdwfl failure + + + +errors +parse/semantics error +libdwfl failure + + + +parse/semantics error +understanding SystemTap errors +libdwfl failure + + + +libdwfl failure +parse/semantics error +understanding SystemTap errors + There was a problem processing the debugging information. In most cases, this error results from the installation of a kernel-debuginfo RPM whose version does not match @@ -180,13 +602,54 @@ probe syscall.open
Run Time Errors and Warnings - + +understainding SystemTap errors +runtime errors/warnings + + + +errors +runtime errors/warnings + + + +runtime errors/warnings +understainding SystemTap errors + + + + Runtime errors and warnings occur when the SystemTap instrumentation has been installed and is collecting data on the system. WARNING: Number of errors: <replaceable>N</replaceable>, skipped probes: <replaceable>M</replaceable> + + + +understainding SystemTap errors +runtime errors/warnings +number of errors: N, skipped probes: M + + + +errors +runtime errors/warnings +number of errors: N, skipped probes: M + + + +runtime errors/warnings +understainding SystemTap errors +number of errors: N, skipped probes: M + + + +number of errors: N, skipped probes: M +runtime errors/warnings +understainding SystemTap errors + Errors and/or skipped probes occurred during this run. Both N and M are @@ -197,12 +660,69 @@ probe syscall.open division by 0 + + + +understainding SystemTap errors +runtime errors/warnings +division by 0 + + + +errors +runtime errors/warnings +division by 0 + + + +runtime errors/warnings +understainding SystemTap errors +division by 0 + + + +division by 0 +runtime errors/warnings +understainding SystemTap errors + + + +invalid division +runtime errors/warnings +understainding SystemTap errors + + The script code performed an invalid division. aggregate element not found + + + +understainding SystemTap errors +runtime errors/warnings +aggregate element not found + + + +errors +runtime errors/warnings +aggregate element not found + + + +runtime errors/warnings +understainding SystemTap errors +aggregate element not found + + + +aggregate element not found +runtime errors/warnings +understainding SystemTap errors + An statistics extractor function other than @count was invoked on an aggregate that has not had any values accumulated yet. -- cgit