public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: mark@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-91-g8fa5f27 Date: Thu, 08 Mar 2012 23:20:00 -0000 [thread overview] Message-ID: <20120308232035.5830.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 8fa5f2719e4ec115486e69364e110a5048c7dfd7 (commit) via 49131a6df3a031f0011256cfa33130afc63c001c (commit) from 76185b64ca769838c08fee2d2efaf1ea5b2628da (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 8fa5f2719e4ec115486e69364e110a5048c7dfd7 Author: Mark Wielaard <mjw@redhat.com> Date: Fri Mar 9 00:10:52 2012 +0100 Cannot use @var DWARF variables in tracepoints, warn, but don't crash. commit 49131a6df3a031f0011256cfa33130afc63c001c Author: Mark Wielaard <mjw@redhat.com> Date: Thu Mar 8 23:32:49 2012 +0100 Make sure @var works for process.mark probes. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 10 ++++++++-- testsuite/systemtap.base/at_var_mark.exp | 13 +++++++++++++ testsuite/systemtap.base/at_var_mark.stp | 19 +++++++++++++++++++ 3 files changed, 40 insertions(+), 2 deletions(-) create mode 100644 testsuite/systemtap.base/at_var_mark.exp create mode 100644 testsuite/systemtap.base/at_var_mark.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-03-08 23:20 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=20120308232035.5830.qmail@sourceware.org \ --to=mark@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).