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-357-g7f02ca9 Date: Sat, 29 Oct 2011 00:25:00 -0000 [thread overview] Message-ID: <20111029002503.12805.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 7f02ca949b99ffba946803fb38c0f9546bc4d9c3 (commit) via b1615c74e19656b6182ff5d81c613ec9f8c57db3 (commit) via 3d69c03f37c05136a01481994e239f1287138f6a (commit) from 93ee09d508e10d054465c63553b30539d70e0c4b (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 7f02ca949b99ffba946803fb38c0f9546bc4d9c3 Author: Josh Stone <jistone@redhat.com> Date: Fri Oct 28 15:42:02 2011 -0700 Add the pattern for label probes in libraries * tapsets.cxx (dwarf_derived_probe::register_patterns): Refactor so that all process[.library] variants get the same set of suffixes. (dwarf_derived_probe::register_function_and_statement_variants): Add the label pattern from here, just as .inline is done. commit b1615c74e19656b6182ff5d81c613ec9f8c57db3 Author: Josh Stone <jistone@redhat.com> Date: Fri Oct 28 15:11:17 2011 -0700 Refactor sdt & plt pattern registration This factors the sdt and plt suffixes away from the various process and process.library prefixes. As a result, we also gain process.plt for probing -c commands. * tapsets.cxx (dwarf_derived_probe::register_sdt_variants): New. (dwarf_derived_probe::register_plt_variants): New. (dwarf_derived_probe::register_patterns): Register sdt and plt for all process/library combinations. * testsuite/semok/plt2.stp: Test that process.plt succeeds with -c * testsuite/semko/plt2.stp: Test that process.plt fails without -c commit 3d69c03f37c05136a01481994e239f1287138f6a Author: Josh Stone <jistone@redhat.com> Date: Fri Oct 28 14:42:23 2011 -0700 plt: Throw an appropriate error for missing $var * tapsets.cxx (plt_expanding_visitor::visit_target_symbol): Throw a semantic_error for missing $var, so it may be caught and chained for later. This ensures that the visitor always has a provide() too. * testsuite/semko/plt1.stp: New, check that missing $var is an error. * testsuite/semok/plt1.stp: New, check that $$name works, as does @defined on a missing $var. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 121 ++++++++++++++++++++++----------------------- testsuite/semko/plt1.stp | 6 ++ testsuite/semko/plt2.stp | 4 ++ testsuite/semok/plt1.stp | 6 ++ testsuite/semok/plt2.stp | 4 ++ 5 files changed, 79 insertions(+), 62 deletions(-) create mode 100755 testsuite/semko/plt1.stp create mode 100755 testsuite/semko/plt2.stp create mode 100755 testsuite/semok/plt1.stp create mode 100755 testsuite/semok/plt2.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-10-29 0:25 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=20111029002503.12805.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).