| 1 |
.\" t |
| 2 |
.TH ERROR::INODE-UPROBES 7stap |
| 3 |
.SH NAME |
| 4 |
error::inode-uprobes \- limitations of inode-uprobes |
| 5 |
|
| 6 |
.SH DESCRIPTION |
| 7 |
|
| 8 |
The uprobes kernel facility introduced in Linux 3.5 aims to supplant the |
| 9 |
earlier out-of-tree utrace patch to enable user-space probing. There |
| 10 |
have been some functional limitations in inode-uprobes that preclude |
| 11 |
some systemtap constructs. Over time, we hope these regressions will |
| 12 |
be corrected. |
| 13 |
|
| 14 |
.TP |
| 15 |
function.return probes |
| 16 |
.IR process.function().return |
| 17 |
probes require "return-probes" or "uretprobes" functionality, which was not |
| 18 |
implemented in the builtin inode-uprobes until kernel 3.10. If you cannot |
| 19 |
upgrade your kernel, consider using |
| 20 |
.IR process.statement() |
| 21 |
probes placed on source line numbers at the function's return statements. |
| 22 |
|
| 23 |
.TP |
| 24 |
function.statement.absolute probes |
| 25 |
In utrace-equipped kernels, systemtap made it possible to address probes |
| 26 |
by literal addresses in the process virtual memory address space. The |
| 27 |
new inode-uprobes does not have this capability. |
| 28 |
|
| 29 |
|
| 30 |
.SH SEE ALSO |
| 31 |
.nh |
| 32 |
.nf |
| 33 |
.IR stap (1), |
| 34 |
.IR http://kernelnewbies.org/Linux_3.5 , |
| 35 |
.IR http://sourceware.org/systemtap/wiki/utrace , |
| 36 |
.IR error::reporting (7stap) |