This is the mail archive of the systemtap-cvs@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


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  7d11d8c982dc14032485285b934e25114a0892cf (commit)
       via  0940fad9d6f648a8021aa0b8fd5bd4cde0d87653 (commit)
      from  6b65ca8125ec140e97099498158a66177c6b50de (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 7d11d8c982dc14032485285b934e25114a0892cf
Author: Josh Stone <jistone@redhat.com>
Date:   Wed Jun 2 17:18:33 2010 -0700

    PR3672 cont'd: Change pretty-print "depth" to mean substructures
    
    We don't follow pointers anymore within a structure.  Now a single '$'
    suffix means we print a shallow view of the structure, with {...} and
    [...] in place of nested arrays/structs.  A double suffix '$$' means we
    print everything contained in the struct.  Longer suffixes no longer
    have meaning, and for now act the same as '$$'.
    
    * tapsets.cxx (dwarf_pretty_print): Lose the "print_depth" field, and
      instead just check if this is a "full" print job.  Pass a bool
      indicating whether we're currently traversing the top-level, so we
      know which structs to expand.  Also wrap it all in try/catch so bad
      pointers don't kill us.

commit 0940fad9d6f648a8021aa0b8fd5bd4cde0d87653
Author: Josh Stone <jistone@redhat.com>
Date:   Wed Jun 2 18:37:55 2010 -0700

    PR11664: Let return/next break out of try/catch
    
    Try-catch works by faking a local "out" label and running the catch
    block.  In the case of return and next, we have a "goto out" without any
    error, so it should be allowed to progress to the real out label.
    
    * translate.cxx (c_unparser::visit_try_block): Reorganize the nested
      labels to allow normal-fallthrough, normal-out, and error-out.
    * testsuite/systemtap.base/overcatcher.stp: New test.

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

Summary of changes:
 tapsets.cxx                              |  113 ++++++++++++++++--------------
 testsuite/systemtap.base/overcatcher.exp |    9 +++
 testsuite/systemtap.base/overcatcher.stp |   23 ++++++
 translate.cxx                            |   23 ++++---
 4 files changed, 106 insertions(+), 62 deletions(-)
 create mode 100644 testsuite/systemtap.base/overcatcher.exp
 create mode 100644 testsuite/systemtap.base/overcatcher.stp


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]