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. release-0.9.5-182-gd0ea46c
Date: Tue, 21 Apr 2009 13:22:00 -0000	[thread overview]
Message-ID: <20090421132221.13606.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  d0ea46ceac2e72fe0b86269ea50c004711148158 (commit)
      from  543b26ed48ac66743ad309ac6cb848a5d377260f (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 d0ea46ceac2e72fe0b86269ea50c004711148158
Author: David Smith <dsmith@redhat.com>
Date:   Tue Apr 21 08:21:34 2009 -0500

    Correctly handle $syscall in process(PID_OR_PATH).syscall.return probes.
    2009-04-21  David Smith  <dsmith@redhat.com>
    
    	* tapsets.cxx (utrace_derived_probe::utrace_derived_probe): If
    	during target-variable-expanding the probe, we added a new block
    	or probe, add them.
    	(utrace_var_expanding_visitor::visit_target_symbol_cached): New
    	function to cache target variables in a generated syscall probe to
    	use in syscall.return probes.
    	(utrace_var_expanding_visitor::visit_target_symbol_context): In a
    	syscall.return probe, you can't access $syscall.  So use
    	visit_target_symbol_cached() to cache the value for use here.
    	* testsuite/systemtap.base/utrace_syscall_args.stp: Test use of
    	$syscall in syscall.return probes.

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

Summary of changes:
 tapsets.cxx                                      |  262 +++++++++++++++++++++-
 testsuite/systemtap.base/utrace_syscall_args.stp |   40 ++++
 2 files changed, 297 insertions(+), 5 deletions(-)


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


                 reply	other threads:[~2009-04-21 13:22 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=20090421132221.13606.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).