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, master, updated. rhel52-ga-365-geff6ac7
Date: Fri, 06 Jun 2008 13:45:00 -0000	[thread overview]
Message-ID: <20080606134527.10651.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, master has been updated
       via  eff6ac721e6a88857d1adea05f703989f5e70839 (commit)
      from  7b53a460d4edb65a110fcbfd18c74f66538277f1 (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 eff6ac721e6a88857d1adea05f703989f5e70839
Author: David Smith <dsmith@redhat.com>
Date:   Fri Jun 6 08:43:59 2008 -0500

    Changed/renamed utrace probes.
    2008-06-06  David Smith  <dsmith@redhat.com>
    
    	* tapsets.cxx (enum utrace_derived_probe_flags): Redefined in
    	terms of probe types instead of utrace events.
    	(utrace_var_expanding_copy_visitor::visit_target_symbol): Uses new
    	utrace_derived_probes_flags values.
    	(utrace_builder::build): Handles new probe types and new
    	utrace_derived_probes_flags values.
    	(utrace_derived_probe_group::emit_probe_decl): Updated to handle
    	new utrace_derived_probe_flags values.
    	(utrace_derived_probe_group::emit_module_decls): Ditto.  Also
    	correctly handles 'begin' events correctly by installing a quiesce
    	handler (instead of running the probe directly).
    	(register_standard_tapsets): Registers updated utrace probe
    	types.
    
    2008-06-06  David Smith  <dsmith@redhat.com>
    
    	* task_finder.c: Added some debug logic.  Use
    	'-DDEBUG_TASK_FINDER' to enable.
    	(stap_utrace_attach): Renamed from '__stp_utrace_attach'.
    	(__stp_utrace_attach_match_filename): Calls callback with
    	notification that this is a process or thread event.
    	(__stp_utrace_attach_match_tsk): Ditto.
    	(__stp_utrace_task_finder_report_clone): Ditto.
    	(__stp_utrace_task_finder_report_exec): Ditto.
    	(stap_utrace_task_finder_report_death): Ditto.
    	(stap_start_task_finder): Ditto.
    	(stap_stop_task_finder): Added debug logic.
    
    2008-06-06  David Smith  <dsmith@redhat.com>
    
    	* systemtap.base/utrace_p4.exp: Updated for utrace probe changes.
    	* systemtap.base/utrace_p5.exp: Ditto.

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

Summary of changes:
 ChangeLog                              |   16 ++
 runtime/ChangeLog                      |   14 ++
 runtime/task_finder.c                  |   92 ++++++----
 tapsets.cxx                            |  293 ++++++++++++++++++++------------
 testsuite/ChangeLog                    |    5 +
 testsuite/systemtap.base/utrace_p4.exp |   27 ++-
 testsuite/systemtap.base/utrace_p5.exp |   50 ++----
 7 files changed, 306 insertions(+), 191 deletions(-)


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


                 reply	other threads:[~2008-06-06 13:45 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=20080606134527.10651.qmail@sourceware.org \
    --to=dsmith@sourceware.org \
    --cc=systemtap-cvs@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).