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-332-g2b300eb Date: Wed, 23 Jun 2010 23:06:00 -0000 [thread overview] Message-ID: <20100623230623.22501.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 2b300ebe599bbfbd8c37d2ec85bace26ada8c1e4 (commit) via d48df0cfe5a083398926493f558c261f2ab56ffa (commit) from 94cbf48e332d87d85592cf774a45b5fa8e9ae027 (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 2b300ebe599bbfbd8c37d2ec85bace26ada8c1e4 Author: Josh Stone <jistone@redhat.com> Date: Wed Jun 23 16:04:25 2010 -0700 Add kernel-dwarf to the pretty-prints tests Since some kernels don't have utrace, we should also exercise the dwarf pretty-printing on a kprobe. commit d48df0cfe5a083398926493f558c261f2ab56ffa Author: Josh Stone <jistone@redhat.com> Date: Wed Jun 23 14:28:16 2010 -0700 PR10830 cont'd: Rename pp1() -> pn() and isolate it The new name is "pn" to evoke "probe name". It is also now isolated in its own tapset file, so it's less likely to be pulled into and conflict with a user's script accidentally. No real code changes here -- it's roughly just s/pp1/pn/ and s/probe_point_listing/probe_name/. ----------------------------------------------------------------------- Summary of changes: tapset-timers.cxx | 4 ++-- tapset/context.stp | 18 ------------------ tapset/pn.stp | 26 ++++++++++++++++++++++++++ tapsets.cxx | 8 ++++---- testsuite/buildok/context-embedded.stp | 2 +- testsuite/buildok/pretty.stp | 13 ++++++++----- testsuite/semok/pretty.stp | 13 ++++++++----- testsuite/systemtap.base/pp.exp | 4 ++-- testsuite/systemtap.base/pp.stp | 2 +- translate.cxx | 16 ++++++++-------- 10 files changed, 60 insertions(+), 46 deletions(-) create mode 100644 tapset/pn.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-06-23 23:06 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=20100623230623.22501.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).