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.2-198-g7d11d8c Date: Thu, 03 Jun 2010 01:48:00 -0000 [thread overview] Message-ID: <20100603014759.9913.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 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
reply other threads:[~2010-06-03 1:48 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=20100603014759.9913.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: linkBe 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).