public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: dsmith@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, dsmith/task_finder2, updated. release-1.6-65-gd0afdcb
Date: Thu, 04 Aug 2011 21:30:00 -0000	[thread overview]
Message-ID: <20110804213011.13876.qmail@sourceware.org> (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  d0afdcbf6bdab884f27f74e0ceb31f0c04b9203c (commit)
      from  580e803219cae2661570748e96a3b710bf651f0d (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 d0afdcbf6bdab884f27f74e0ceb31f0c04b9203c
Author: David Smith <dsmith@redhat.com>
Date:   Thu Aug 4 16:29:53 2011 -0500

    Updated with ftrace_based function probe.
    
    * runtime/stp_utrace.c: Switched from kprobes-based function probe to
      ftrace-based function probe.
    * runtime/task_finder2.c: Switched back to allocating path buffers.
      Ifdef'ed out some debug prints.
    * tapset-utrace.cxx (utrace_derived_probe_group::emit_probe_decl): Updated
      emitted syscall probe code for STP_TASK_FINDER2.
      (utrace_derived_probe_group::emit_module_decls): Ditto.

-----------------------------------------------------------------------

Summary of changes:
 runtime/stp_utrace.c   |   28 +++++++++++++++++-----------
 runtime/task_finder2.c |   32 +++++++++++---------------------
 tapset-utrace.cxx      |   18 +++++++++++++++++-
 3 files changed, 45 insertions(+), 33 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2011-08-04 21:30 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=20110804213011.13876.qmail@sourceware.org \
    --to=dsmith@sourceware.org \
    --cc=systemtap-cvs@sourceware.org \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).