diff options
author | Frank Ch. Eigler <fche@elastic.org> | 2008-11-29 09:27:43 -0500 |
---|---|---|
committer | Frank Ch. Eigler <fche@elastic.org> | 2008-11-29 09:27:43 -0500 |
commit | 7d091090a01e61e1fd94d65c56e9df11e9ba2f6e (patch) | |
tree | 70ab8a5205383b586983b11ae3a317cbc258aceb | |
parent | fd2aeae9e2d04d2cf417a32f98257041e8ff0e2c (diff) | |
download | systemtap-steved-7d091090a01e61e1fd94d65c56e9df11e9ba2f6e.tar.gz systemtap-steved-7d091090a01e61e1fd94d65c56e9df11e9ba2f6e.tar.xz systemtap-steved-7d091090a01e61e1fd94d65c56e9df11e9ba2f6e.zip |
NEWS: add blurbs re "stap -t" skippage and shared library probing
-rw-r--r-- | NEWS | 15 |
1 files changed, 15 insertions, 0 deletions
@@ -1,5 +1,20 @@ * What's new +- A serious problem associated with user-space probing in shared libraries + was corrected, making it now possible to experiment with probe shared + libraries. Assuming dwarf debugging information is installed, use this + twist on the normal syntax: + + probe process("/lib64/libc-2.8.so").function("....") { ... } + + This would probe all threads that call into that library. Running + "stap -c CMD" or "stap -x PID" naturally restricts this to the target + command+descendants only. + +- For scripts that sometimes terminate with excessive "skipped" probes, + rerunning the script with "-t" (timing) will print more details about + the skippage reasons. + - Symbol tables and unwind (backtracing) data support were formerly compiled in for all probed modules as identified by the script (kernel; module("name"); process("file")) plus those listed by the |