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.3-181-g653e6a9 Date: Tue, 05 Oct 2010 01:08:00 -0000 [thread overview] Message-ID: <20101005010846.18530.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 653e6a9a860d2cdf71a3be5eb0ec91c3606a7f58 (commit) from 0ac3dce18d9bcadff5f2f5f9274a7b40889d1d1a (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 653e6a9a860d2cdf71a3be5eb0ec91c3606a7f58 Author: Josh Stone <jistone@redhat.com> Date: Mon Oct 4 17:56:26 2010 -0700 PR11739: Add an STP_ALIBI flag Primarily just for testing purposes, define STP_ALIBI to shortcut all probe handlers, so they're nothing but an atomic_inc. It prints a hit report similar to STP_TIMING at the end. Note that any logic that would have called exit() will also be blocked, so you need other ways to end the script: SIGINT, finished -c, etc. * tapsets.cxx (common_probe_entryfn_prologue): #ifdef STP_ALIBI, reduce the probe handler to just an atomic_inc(). (common_probe_entryfn_epilogue): Close the #ifdef from above. * translate.cxx (translate_pass): Add an atomic_t to stap_probe for STP_ALIBI to track probe hits. (c_unparser::emit_module_exit): Print alibi hit-report. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 6 ++++++ translate.cxx | 25 +++++++++++++++++++++---- 2 files changed, 27 insertions(+), 4 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-10-05 1:08 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=20101005010846.18530.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).