public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, dsmith/task_finder2, updated. release-1.6-393-gdb7dcdf
Date: Thu, 03 Nov 2011 16:34: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, dsmith/task_finder2 has been updated
       via  db7dcdffc5687db14e44cb08896a173e60d8e3ac (commit)
      from  6d7287ac9e73d65401c2679e2531e37e0bf19ada (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 db7dcdffc5687db14e44cb08896a173e60d8e3ac
Author: David Smith <>
Date:   Thu Nov 3 11:19:04 2011 -0500

    Added 'autoconf' tests to figure out which new utrace implementation to use.
    * runtime/autoconf-utrace-via-ftrace.c: New autoconf test.
    * runtime/autoconf-utrace-via-tracepoints.c: Ditto.
    * buildrun.cxx (compile_pass): Use 2 new autoconf tests.
    * runtime/stp_utrace.c: Handle STAPCONF_UTRACE_VIA_TRACEPOINTS and
    * runtime/task_finder.c: Ditto.


Summary of changes:
 buildrun.cxx                              |    3 ++
 runtime/autoconf-utrace-via-ftrace.c      |   52 +++++++++++++++++++++++++++++
 runtime/autoconf-utrace-via-tracepoints.c |   50 +++++++++++++++++++++++++++
 runtime/stp_utrace.c                      |   50 ++++++++++++++++++++++++++-
 runtime/task_finder.c                     |   49 ++++++++++++++++-----------
 5 files changed, 182 insertions(+), 22 deletions(-)
 create mode 100644 runtime/autoconf-utrace-via-ftrace.c
 create mode 100644 runtime/autoconf-utrace-via-tracepoints.c

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2011-11-03 16:34 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).