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-169-gf1b9a51 Date: Wed, 29 Sep 2010 20:57:00 -0000 [thread overview] Message-ID: <20100929205746.32504.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 f1b9a51a28e577eb6c37af1228e9b84983c04432 (commit) via 4c5d1300de1c71181c1915bf0eb4a3c0ba8ad374 (commit) via 1c9bce2dfcff96c02a30786a479ae125f6317ba9 (commit) from f50adc78bad022ae53410bbbf52b38e426447844 (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 f1b9a51a28e577eb6c37af1228e9b84983c04432 Author: Josh Stone <jistone@redhat.com> Date: Wed Sep 29 13:51:30 2010 -0700 Improve the derivation output of STP_TIMING We can't assume location[0] from the probes in the derivation chain, as it may include e.g. an alias with multiple expansions. Instead, a new "base_pp" member tracks which probe_point actually led to each step of the derivation. * elaborate.cxx (derived_probe::derived_probe): Remember the unmodified probe_point as base_pp, esp. before any components are rewritten. (derived_probe::collect_derivation_pp_chain): New, collect base_pp. * translate.cxx (c_unparser::emit_module_exit): Use the pp chain in STP_TIMING output. commit 4c5d1300de1c71181c1915bf0eb4a3c0ba8ad374 Author: Josh Stone <jistone@redhat.com> Date: Wed Sep 29 13:36:51 2010 -0700 Standardize how derived_probes dupe their location A few of the derived_probe subclasses make duplicates of their probe_point so they can rewrite it to something more specific. This patch standardizes that behavior. It also fixes kprobe_derived_probe and hwbkpt_derived_probe, which were rewriting components without making a copy first. commit 1c9bce2dfcff96c02a30786a479ae125f6317ba9 Author: Josh Stone <jistone@redhat.com> Date: Wed Sep 29 12:45:40 2010 -0700 Remove the derived_probe ctor lacking a probe_point In practice, our derived_probes always have a specific probe_point that they originate from, so don't let it be omitted. ----------------------------------------------------------------------- Summary of changes: elaborate.cxx | 26 +++++++++++++------------- elaborate.h | 5 +++-- staptree.h | 1 + tapset-been.cxx | 1 - tapset-mark.cxx | 2 +- tapset-perfmon.cxx | 2 +- tapset-utrace.cxx | 2 +- tapsets.cxx | 8 ++++---- task_finder.cxx | 2 +- translate.cxx | 8 ++++---- 10 files changed, 29 insertions(+), 28 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-09-29 20:57 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=20100929205746.32504.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).