public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-86-g5592739
Date: Wed, 07 Mar 2012 19:24:00 -0000	[thread overview]
Message-ID: <> (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  559273928633e8d71c45399fb173fdd05a1c6db8 (commit)
       via  bfa7e523ab8cd891a2a3f24c1540021665947b5d (commit)
       via  cc9001af0a5fa811ddf0e44439c7cddf465db945 (commit)
      from  b05fd5898ac3a127f7843943d0304ce37dcdd5fd (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 559273928633e8d71c45399fb173fdd05a1c6db8
Merge: b05fd58 bfa7e52
Author: Mark Wielaard <>
Date:   Wed Mar 7 20:11:46 2012 +0100

    Merge branch 'at_var'

commit bfa7e523ab8cd891a2a3f24c1540021665947b5d
Author: Mark Wielaard <>
Date:   Wed Mar 7 19:58:12 2012 +0100

    PR13784 Allow defining a diffent CU source in @var.
    Add cu_name to struct target_symbol. Set it in parse_target_symbol
    to the string after @ in @var("somevar@some/src/file.c"). Make
    target_symbol::sym_name() aware of @cu_name postfix (don't return it).
    Add dwarf_var_expanding_visitor::getcuscope() which figures out the
    CU DIE to use as scope if target_symbol has cu_name part. Extend
    global_var.exp test to show new capability.

commit cc9001af0a5fa811ddf0e44439c7cddf465db945
Author: Mark Wielaard <>
Date:   Tue Mar 6 17:34:36 2012 +0100

    Introduce @var("varname") as alternative syntax for $varname.
    Adds a field target_name and a method sym_name() to struct target_symbol
    to be used by the parser and tapsets translator so $name and @var("name")
    can be used interchanably. Adds a testcase at_var.exp to test this for
    various combinations of uprobes, kprobes, parameters, variables, arrays,
    fields access, pretty printing and taking addresses.


Summary of changes:
 parse.cxx                               |   33 ++++++++++++++--
 staptree.cxx                            |   14 +++++++
 staptree.h                              |    3 +
 tapset-utrace.cxx                       |    2 +-
 tapsets.cxx                             |   62 +++++++++++++++++++++++++-----
 testsuite/systemtap.base/at_var.c       |   27 +++++++++++++
 testsuite/systemtap.base/at_var.exp     |   34 +++++++++++++++++
 testsuite/systemtap.base/at_var.stp     |   42 +++++++++++++++++++++
 testsuite/systemtap.base/global_var.exp |   15 ++++++-
 testsuite/systemtap.base/global_var.stp |   22 ++++++++++-
 10 files changed, 234 insertions(+), 20 deletions(-)
 create mode 100644 testsuite/systemtap.base/at_var.c
 create mode 100644 testsuite/systemtap.base/at_var.exp
 create mode 100644 testsuite/systemtap.base/at_var.stp

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-03-07 19:24 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:

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

  git send-email \ \ \ \ \

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