diff options
| author | fche <fche> | 2008-02-19 02:48:02 +0000 |
|---|---|---|
| committer | fche <fche> | 2008-02-19 02:48:02 +0000 |
| commit | 1ada6f08ba42f3c1a2f7986f1ad955fd79e06e41 (patch) | |
| tree | 4bb6811a833d9cff1a7f6167f5c7929d4c467e4c /NEWS | |
| parent | cc8090b7e5b9c12616ec5f75195488b9a2737f80 (diff) | |
| download | systemtap-steved-1ada6f08ba42f3c1a2f7986f1ad955fd79e06e41.tar.gz systemtap-steved-1ada6f08ba42f3c1a2f7986f1ad955fd79e06e41.tar.xz systemtap-steved-1ada6f08ba42f3c1a2f7986f1ad955fd79e06e41.zip | |
2008-02-18 Frank Ch. Eigler <fche@elastic.org>
* NEWS, stapprobes.5.in: Document basic (non-symbolic prototype)
user-space probe points.
Diffstat (limited to 'NEWS')
| -rw-r--r-- | NEWS | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -1,5 +1,16 @@ * What's new in version 0.6 / 0.6.1 +- Prototype support for user-space probing is showing some progress. + No symbolic notations are supported yet (so no probing by function names, + file names, process names, and no access to $context variables), but at + least it's something: + + probe process(PID).statement(ADDRESS).absolute { } + + This will set a uprobe on the given process-id and given virtual address. + The proble handler runs in kernel-space as usual, and can generally use + existing tapset functions. + - Crash utility can retrieve systemtap's relay buffer from a kernel dump image by using staplog which is a crash extension module. To use this feature, type commands as below from crash(8)'s command line: |