summaryrefslogtreecommitdiffstats
path: root/stapprobes.5.in
diff options
context:
space:
mode:
authorFrank Ch. Eigler <fche@elastic.org>2008-08-11 17:34:47 -0400
committerFrank Ch. Eigler <fche@elastic.org>2008-08-11 17:34:47 -0400
commit42e740602dbb7960e11b0bbf9053e95e8a1cb1e5 (patch)
treeaa32f56c7c5b1838e9d80bec2c15325c71742660 /stapprobes.5.in
parent3213d0891c826f16ba727a3e863075e2922666a0 (diff)
parent79640c29c5bcf8de20f013dcc80e1a9c7a93811f (diff)
downloadsystemtap-steved-42e740602dbb7960e11b0bbf9053e95e8a1cb1e5.tar.gz
systemtap-steved-42e740602dbb7960e11b0bbf9053e95e8a1cb1e5.tar.xz
systemtap-steved-42e740602dbb7960e11b0bbf9053e95e8a1cb1e5.zip
Merge commit 'origin/master' into pr4225
* commit 'origin/master': (34 commits) PR5049: fix overbroad effects of naive "*" prefixing; instead use optional "*/" only. stap-serverd was incorectly determining that the server could stapprobes man page: clarify statement(NUM).absolute and process("path") searching PR5049: prefix with "*" any filenames given in "fn@filename:line" probes Indentation fix. Redirect stderr gets redircted so warnings don't let example script run fail. PR6835. io/io_submit.stp: Fix #! start. Convert to normal line-ending. PR2895. Add proper #! /usr/bin/env stap line. Make example scripts executable. Use INSTALL_PROGRAM, not INSTALL_DATA for executable .stp scripts. example index: only warn if old, do not regenerate Start/stop the systemtap server from systemtap.exp and not in the top level Makefile. Lower statement wildcard test matching threshold. Moved details of utrace detach to stap_utrace_detach(). Saves thread vma information. Always generate examples indexes and install examples from srcdir. Refer to srcdir spec file Makefile so make rpm works when builddir != srcdir. Add index of subsystem and keywords at top of HTML indexes. Don't output output, exits, status line in indexes (mentioned in descriptions). Disable chmodding of samples/kmalloc-top in spec file since it isn't installed. Make sure examples indexes are always generated in builddir. ...
Diffstat (limited to 'stapprobes.5.in')
-rw-r--r--stapprobes.5.in24
1 files changed, 17 insertions, 7 deletions
diff --git a/stapprobes.5.in b/stapprobes.5.in
index 24075248..d20ea006 100644
--- a/stapprobes.5.in
+++ b/stapprobes.5.in
@@ -292,9 +292,10 @@ 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.
+If it does not match as is, an implicit "*/" is optionally added
+.I before
+the pattern, so that a script need only name the last few components
+of a possibly long source directory path.
.IP \(bu 4
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 ":"
@@ -305,9 +306,16 @@ All the lines in the function can be matched with ":*".
A range of lines x through y can be matched with ":x-y".
.PP
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.
+address. Such an address may be found from symbol tables of the
+appropriate kernel / module object file. It is verified against
+known statement code boundaries, and will be relocated for use at
+run time.
+.PP
+In guru mode only, absolute kernel-space addresses may be specified with
+the ".absolute" suffix. Such an address is considered already relocated,
+as if it came from
+.BR /proc/kallsyms ,
+so it cannot be checked against statement/instruction boundaries.
.PP
Some of the source-level context variables, such as function parameters,
locals, globals visible in the compilation unit, may be visible to
@@ -412,7 +420,9 @@ probe gets called for every single step of the process described by PID or PATH.
.PP
Note that
.I PATH
-pathnames must be absolute.
+names refer to executables that are searched the same way shells do: relative
+to the working directory if they contain a "/" character, otherwise in
+.BR $PATH .
.SS PROCFS