public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-87-g54e9f06
Date: Thu, 08 Mar 2012 14:22:00 -0000	[thread overview]
Message-ID: <20120308142233.1566.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  54e9f0623713e7f32c9870baad5a5d5c06c2fd22 (commit)
      from  559273928633e8d71c45399fb173fdd05a1c6db8 (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 54e9f0623713e7f32c9870baad5a5d5c06c2fd22
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Mar 8 15:20:08 2012 +0100

    Select most specific CU srcfile that matches @var("var@src") specification.
    
    dwarf_var_expanding_visitor::getcuscope: If there is a perfect match
    select that CU, otherwise, select the CU srcfile that is most specific
    (matching path/src file lenght is shortest).

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

Summary of changes:
 tapsets.cxx                                    |   30 +++++++++++++++++------
 testsuite/systemtap.base/global_var_kernel.exp |   10 ++++++++
 testsuite/systemtap.base/global_var_kernel.stp |    8 ++++++
 3 files changed, 40 insertions(+), 8 deletions(-)
 create mode 100644 testsuite/systemtap.base/global_var_kernel.exp
 create mode 100644 testsuite/systemtap.base/global_var_kernel.stp


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


                 reply	other threads:[~2012-03-08 14: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=20120308142233.1566.qmail@sourceware.org \
    --to=mark@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).