diff options
-rw-r--r-- | ChangeLog | 16 | ||||
-rw-r--r-- | NEWS | 28 | ||||
-rw-r--r-- | tapset/ChangeLog | 5 | ||||
-rw-r--r-- | tapset/signal.stp | 37 |
4 files changed, 73 insertions, 13 deletions
@@ -1,3 +1,19 @@ +2009-02-04 Mark Wielaard <mjw@redhat.com> + + * NEWS: process().mark(), sys/sdt.h and dtrace compatibility script. + +2009-02-04 Mark Wielaard <mjw@redhat.com> + + * NEWS: Mention run-stap. + +2009-02-04 Mark Wielaard <mjw@redhat.com> + + * NEWS: Add Beginner Guide. + +2009-02-04 Mark Wielaard <mjw@redhat.com> + + * NEWS: Mention SystemTap Tapset Reference Manual. + 2009-02-03 Frank Ch. Eigler <fche@elastic.org> PR6961/9810. @@ -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 diff --git a/tapset/ChangeLog b/tapset/ChangeLog index 1a7df352..570d3697 100644 --- a/tapset/ChangeLog +++ b/tapset/ChangeLog @@ -1,3 +1,8 @@ +2009-02-04 K Prasad <prasad@linux.vnet.ibm.com> + + PR 7030. + * signal.stp: handle functions inlined in 2.6.27+ + 2009-02-03 Frank Ch. Eigler <fche@elastic.org> PR 6961/9810. diff --git a/tapset/signal.stp b/tapset/signal.stp index 7f932e77..8c125e80 100644 --- a/tapset/signal.stp +++ b/tapset/signal.stp @@ -84,21 +84,17 @@ probe _signal.send.part4 = kernel.function("specific_send_sig_info") %( kernel_v > "2.6.25" %? probe _signal.send.part1 = kernel.function("send_signal") { - name = "__group_send_sig_info" + if ($group == 1) { + name = "__group_send_sig_info" + shared = 1 + } + else if ($group == 0) { + name = "specific_send_sig_info" + shared = 0 + } sig = $sig task = $t sinfo = $info - shared = 1 - send2queue = 0 -} - -probe _signal.send.part4 = kernel.function("send_signal") -{ - name = "specific_send_sig_info" - sig = $sig - task = $t - sinfo = $info - shared = 0 send2queue = 0 } %) @@ -139,6 +135,22 @@ probe signal.send.return = _signal.send.*.return * and sent by user using something other than kill() * */ +%( kernel_v > "2.6.25" %? +probe _signal.send.part1.return = kernel.function("send_signal").return +{ + if ($group == 1) { + name = "__group_send_sig_info" + shared = 1 + } + else if ($group == 0) { + name = "specific_send_sig_info" + shared = 0 + } + send2queue = 0 +} +%) + +%( kernel_v <= "2.6.25" %? probe _signal.send.part1.return = kernel.function("__group_send_sig_info").return { name = "__group_send_sig_info" @@ -153,7 +165,6 @@ probe _signal.send.part4.return = kernel.function("specific_send_sig_info").retu send2queue = 0 } -%( kernel_v <= "2.6.25" %? /* * - return 0 if the signal is either sucessfully added into the * sigqueue of receiving process or a SI_TIMER entry is already |