[SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-397-g140be17

[jistone at sourceware dot org]

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  140be17a163dfa6beb5cf1e2f8981cb60184ed44 (commit)
       via  47088594133cc7f0146b0743600e8f41a2192aa7 (commit)
       via  14a978523a98c8bfb4bd2f82b7625ff8c900ac31 (commit)
      from  cf9a5802add2894f4c1cc8699b7fbb4402dd4336 (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 140be17a163dfa6beb5cf1e2f8981cb60184ed44
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Jul 2 22:19:11 2010 -0700

    PR11785 (partial): Better detection of kretprobe data types
    
    It's a bit less of a kludge now, letting the one who expanded the $var
    determine the type to be saved.
    
    * tapsets.cxx (dwarf_var_expanding_visitor::gen_kretprobe_saved_return):
      Determine the kretprobe data type from the expression itself.
      (dwarf_var_expanding_visitor::visit_target_symbol_context): Dwarf
      context vars become an sprintf, and thus are pe_string.
      (dwarf_var_expanding_visitor::visit_target_symbol): Regular dwarf vars
      get their type from the functiondecl (practically it's always pe_long).
      (dwarf_pretty_print::expand): Pretty-printing is always a string.
    * testsuite/semok/kretprobe-data.stp: Test the various type resolution.

commit 47088594133cc7f0146b0743600e8f41a2192aa7
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Jul 2 21:52:22 2010 -0700

    Make debugging easier without installing
    
    When using run-stap, it was a pain to replicate the same environment in
    gdb after a crash.  Now you can use the environment variable DEBUG_STAP=1.
    
    $ ./run-stap -e 'something touchy...'
    (crash!)
    $ env DEBUG_STAP=1 !!
    (gdb, ready to go with the same args)

commit 14a978523a98c8bfb4bd2f82b7625ff8c900ac31
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Jul 2 21:40:53 2010 -0700

    PR11785 (partial): add grace to tracepoint $$parms$
    
    Tracepoint args with base types should not be dereferenced at all, but
    the pretty-printing is not wise enough to know that.  Thankfully we were
    already blocking the pretty-printing from such vars, but the error was
    turning into an assertion failure in $$parms$.
    
    So rather than asserting, for now just turn them into "=?" like dwarf
    probes do with such failure.  Later we can try to make pretty printing
    work with such base-typed tracepoint $vars.
    
    * tapsets.cxx
      (tracepoint_var_expanding_visitor::visit_target_symbol_context):
      Don't assert that there aren't errors, just squash them.
    * testsuite/semok/pretty2.stp: Exercise lots of tracepoints.

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

Summary of changes:
 run-stap.in                        |    6 +++++-
 tapsets.cxx                        |   36 +++++++++++++++++++++++-------------
 testsuite/semok/kretprobe-data.stp |    9 +++++++++
 testsuite/semok/pretty2.stp        |   11 +++++++++++
 4 files changed, 48 insertions(+), 14 deletions(-)
 create mode 100755 testsuite/semok/kretprobe-data.stp
 create mode 100755 testsuite/semok/pretty2.stp


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