public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-192-gd87623a
Date: Sat, 07 Nov 2009 00:12:00 -0000	[thread overview]
Message-ID: <20091107001243.11719.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  d87623a1515eada2bd7809b370bf8e7a3294c985 (commit)
      from  079915a57182ed3e5981190ccf8216c674aa4406 (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 d87623a1515eada2bd7809b370bf8e7a3294c985
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Nov 6 16:01:10 2009 -0800

    Constrain $var-checking for -L of .return probes
    
    Normally, using a $var in a return probe create a matching entry probe
    to save the value.  We don't want all this machinery though when we're
    just checking the accessibility of a $var for -L mode.
    
    * tapsets.cxx (dwarf_derived_probe::saveargs): Save/restore has_return
      while the $var accesses are attempted.

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

Summary of changes:
 tapsets.cxx |   20 ++++++++++----------
 1 files changed, 10 insertions(+), 10 deletions(-)


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


                 reply	other threads:[~2009-11-07  0:12 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=20091107001243.11719.qmail@sourceware.org \
    --to=jistone@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).