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-0.9-92-g046e719 Date: Tue, 10 Mar 2009 01:12:00 -0000 [thread overview] Message-ID: <20090310011220.21920.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 046e719028ae6b037fb7342b7d0764985bfaf408 (commit) via c3add01f692e698995a62c13e154bab35d9212df (commit) from ba4e4ff4ba0206bb707538bbfb5e07d3cca33d5b (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 046e719028ae6b037fb7342b7d0764985bfaf408 Author: Josh Stone <jistone@redhat.com> Date: Mon Mar 9 17:37:14 2009 -0700 Add tracepoint $$parms alias for $$vars For parity with the DWARF probes, this makes tracepoints also define $$parms, which has the same value as $$vars (since tracepoints are missing the concept of $$locals). commit c3add01f692e698995a62c13e154bab35d9212df Author: Josh Stone <jistone@redhat.com> Date: Mon Mar 9 17:23:05 2009 -0700 Update location of c->probe_point reset The probe_point clear was nested in the overload processing code, I believe accidentally. This just makes it always cleared on probe exit. ----------------------------------------------------------------------- Summary of changes: stapprobes.5.in | 2 +- tapsets.cxx | 10 ++++++---- 2 files changed, 7 insertions(+), 5 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-03-10 1:12 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=20090310011220.21920.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).