summaryrefslogtreecommitdiffstats
path: root/NEWS
diff options
context:
space:
mode:
Diffstat (limited to 'NEWS')
-rw-r--r--NEWS28
1 files changed, 28 insertions, 0 deletions
diff --git a/NEWS b/NEWS
index 443ec694..88e162ef 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,33 @@
* What's new
+- process().mark() probes are now possible to trace static user space
+ markers put in programs with the STAP_PROBE macro using the new
+ sys/sdt.h include file. This also provides dtrace compatible markers
+ through DTRACE_PROBE and an associated python 'dtrace' script that
+ can be used in builds based on dtrace that need dtrace -h or -G
+ functionality.
+
+- For those that really want to run stap from the build tree there is
+ now the 'run-stap' script in the top-level build directory that sets
+ up the SYSTEMTAP_TAPSET, SYSTEMTAP_RUNTIME, SYSTEMTAP_STAPRUN, and
+ SYSTEMTAP_STAPIO environment variables (installing systemtap, in a
+ local prefix, is still recommended for common use).
+
+- Systemtap now comes with a new Beginners Guide that walks the user
+ through their first steps setting up stap, understanding how it all
+ works, introduces some useful scripts and describes some common
+ pitfalls. It isn't created by default since it needs a Publican
+ setup, but full build instructions can be found in the wiki:
+ http://sourceware.org/systemtap/wiki/PublicanQuikHowto
+ An online version can be found at:
+ http://sourceware.org/systemtap/SystemTap_Beginners_Guide.pdf
+
+- Standard tapsets included with Systemtap were modified to include
+ extractable documentation information based on the kernel-doc
+ infrastructure. When configured --enabled-docs a HTML and PDF
+ version of the Tapset Reference Manual is produced explaining probes
+ defined in each tapset.
+
- The systemtap client and compile server are now available.
These allow you to compile a systemtap module on a host other than
the one which it will be run, providing the client and server