public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-212-g4107dbc
Date: Tue, 08 May 2012 18:02:00 -0000	[thread overview]
Message-ID: <> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  4107dbc2c88536c3374a68948c7344af8c8e75aa (commit)
      from  b05f026cdfc68b8c08bc7b7ba72a22b5bb2e0ec6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 4107dbc2c88536c3374a68948c7344af8c8e75aa
Author: Mark Wielaard <>
Date:   Tue May 8 19:59:07 2012 +0200

    PR14079 - caller() pass-4 error if no uretprobes in script
    caller() is odd in that it tries to do both kernel and user caller.
    There is no ucaller(). Move it into its own tapset and include the
    right uprobes related structures.
    * runtime/uprobes-inc.h: New include file to be included in ...
    * runtime/stack.c: here and ...
    * tapset/context-caller.stp: here. New tapset, with just the caller context
      function, removed from ...
    * tapset/context-unwind.stp: here.
    * doc/SystemTap_Tapset_Reference/tapsets.tmpl: Also include context-caller.stp.


Summary of changes:
 doc/SystemTap_Tapset_Reference/tapsets.tmpl |    1 +
 runtime/stack.c                             |   14 +--------
 runtime/uprobes-inc.h                       |   13 ++++++++
 tapset/context-caller.stp                   |   44 +++++++++++++++++++++++++++
 tapset/context-unwind.stp                   |   29 -----------------
 5 files changed, 59 insertions(+), 42 deletions(-)
 create mode 100644 runtime/uprobes-inc.h
 create mode 100644 tapset/context-caller.stp

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-05-08 18:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).