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.6-226-g52dd8bd
Date: Sat, 17 Sep 2011 00:14:00 -0000	[thread overview]
Message-ID: <20110917001451.20747.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  52dd8bd8b27650431f3362312411891fde7b3c58 (commit)
       via  40a0c64ebad7c96fc826c8eed172485126cb870a (commit)
       via  3805a31e77820efceeae0321c30be196edb05af2 (commit)
       via  91699a70d5a64e5de7ca4bde2bd6d77818e89e74 (commit)
      from  01cfbeb43559e5a93eda648fc81d4aa102e6cb13 (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 52dd8bd8b27650431f3362312411891fde7b3c58
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Sep 16 16:45:15 2011 -0700

    PR12136: Test a @cast to type sdt::string
    
    This test would previously fail to find std::string, as that type is not
    at the top level of the CU in the debuginfo, but rather nested under the
    DIE for the std namespace.  It should now be found.
    
    Note however that this test is currently failing for me due to an
    apparently bad argument calculation.  The @cast in the SDT probe looks
    good, but from the function probe it's getting a bad pointer for $str.
    It's OK on F15 i686, but not on F15 x86_64.  I think this issue is
    distinct from what I'm fixing, but it need further investigation...

commit 40a0c64ebad7c96fc826c8eed172485126cb870a
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Sep 16 15:59:45 2011 -0700

    Fill in @cast default module from SDT
    
    If a @cast in SDT context does not have a specified source for type
    info, then we should infer it as the SDT's module, as we do for normal
    DWARF-based probes.
    
    * tapsets.cxx (sdt_uprobe_var_expanding_visitor::visit_cast_op): If the
      @cast module isn't already set, use the SDT module.
      (sdt_kprobe_var_expanding_visitor::visit_cast_op): Ditto.

commit 3805a31e77820efceeae0321c30be196edb05af2
Author: Josh Stone <jistone@redhat.com>
Date:   Wed Aug 24 16:21:38 2011 -0700

    PR12136: Load nested types for C++ CUs
    
    For C++ compile units only, check for nested type definitions within
    namespaces, structures, and classes.  This allows @cast to have access
    to types like "std::string".
    
    * dwflpp.cxx (dwflpp::global_alias_caching_callback): Take a flag
      has_inner_types to indicate that we should recurse, and a prefix to
      specify what we've already recursed into.
      (dwflpp::iterate_over_globals): Check whether we're in C++, then do
      the real work in the new iterate_over_types.
      (dwflpp::iterate_over_types): Do the work that iterate_over_globals
      used to handle, without assuming that we're starting in a top CU.

commit 91699a70d5a64e5de7ca4bde2bd6d77818e89e74
Author: Josh Stone <jistone@redhat.com>
Date:   Tue Aug 23 16:59:16 2011 -0700

    Improve scope splitting in function specs
    
    We now take care to only split "::" separators that are outside of any
    template specification.  So "std::foo<std::bar>" becomes only two
    components, "std" and "foo<std::bar>".
    
    * util.cxx (tokenize_cxx): Split on "::" only outside of templates.
    * tapsets.cxx (dwarf_query::parse_function_spec): Use tokenize_cxx.

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

Summary of changes:
 dwflpp.cxx                                         |   48 ++++++++++++++++----
 dwflpp.h                                           |   10 +++-
 tapsets.cxx                                        |   38 +++++++++++++---
 testsuite/systemtap.base/cast-scope.cxx            |   17 +++++++
 .../systemtap.base/{inherit.exp => cast-scope.exp} |   17 +++----
 testsuite/systemtap.base/cast-scope.stp            |   10 ++++
 util.cxx                                           |   31 +++++++++++++
 util.h                                             |    1 +
 8 files changed, 144 insertions(+), 28 deletions(-)
 create mode 100644 testsuite/systemtap.base/cast-scope.cxx
 copy testsuite/systemtap.base/{inherit.exp => cast-scope.exp} (60%)
 create mode 100644 testsuite/systemtap.base/cast-scope.stp


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


                 reply	other threads:[~2011-09-17  0:14 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=20110917001451.20747.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).