| 1 |
.\" t |
| 2 |
.TH WARNING::PROCESS-TRACKING 7stap |
| 3 |
.SH NAME |
| 4 |
warning::process-tracking \- process-tracking facilities are not available |
| 5 |
|
| 6 |
.\" macros |
| 7 |
.de SAMPLE |
| 8 |
|
| 9 |
.nr oldin \\n(.i |
| 10 |
.br |
| 11 |
.RS |
| 12 |
.nf |
| 13 |
.nh |
| 14 |
.. |
| 15 |
.de ESAMPLE |
| 16 |
.hy |
| 17 |
.fi |
| 18 |
.RE |
| 19 |
.in \\n[oldin]u |
| 20 |
|
| 21 |
.. |
| 22 |
|
| 23 |
.SH DESCRIPTION |
| 24 |
These errors and warnings occur when the kernel systemtap is running on |
| 25 |
lacks support for user-space process tracking facilities. |
| 26 |
|
| 27 |
.SS COMPILE-TIME ERROR |
| 28 |
The error |
| 29 |
.SAMPLE |
| 30 |
ERROR: user-space process-tracking facilities not available |
| 31 |
.ESAMPLE |
| 32 |
occurs when the script contains a uprobes probe point that the current |
| 33 |
kernel does not support. |
| 34 |
|
| 35 |
.SS RUNTIME WARNINGS |
| 36 |
.PP |
| 37 |
The warning, |
| 38 |
.SAMPLE |
| 39 |
WARNING: process-tracking facilities are not available in this kernel |
| 40 |
.ESAMPLE |
| 41 |
and the related message, |
| 42 |
.SAMPLE |
| 43 |
WARNING: cannot track target in process '...' |
| 44 |
.ESAMPLE |
| 45 |
both occur at runtime when running on a kernel (generally an older |
| 46 |
version) that has neither utrace functionality nor an acceptable |
| 47 |
substitute. |
| 48 |
.PP |
| 49 |
The script should still load and run. However, probes that rely on |
| 50 |
availability of process-tracking facilities will silently fail to |
| 51 |
trigger. |
| 52 |
|
| 53 |
.SH RESOLVING THE ISSUE |
| 54 |
If process-tracking functionality is absolutely necessary, either a |
| 55 |
kernel version newer than 3.5 is needed, or an older version must be |
| 56 |
compiled with appropriate utrace patches. |
| 57 |
|
| 58 |
.SH SEE ALSO |
| 59 |
.nh |
| 60 |
.nf |
| 61 |
.IR stap (1), |
| 62 |
.IR error::reporting (7stap) |