public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.4-205-g84fef8e Date: Sun, 27 Mar 2011 04:01:00 -0000 [thread overview] Message-ID: <20110327040110.1908.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 84fef8ee4e51ccfabc544aaa0b747cbf87a4c8f0 (commit) from a691939c63a136c138f9ad87094a37e5c59c912c (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 84fef8ee4e51ccfabc544aaa0b747cbf87a4c8f0 Author: Frank Ch. Eigler <fche@redhat.com> Date: Sat Mar 26 23:59:24 2011 -0400 sdt_v3: avoid misleading warning on complex operands Roland reported seeing the "Downgrading SDT_V2 probe argument to dwarf ..." warning message on an ambitious SDT_V3 object file. The message is not applicable, since there is no dwarf emitted at all for SDT_V3. * tapsets.cxx (sdt_uprobe_var_expanding_visitor::visit_target_symbol_arg): Remove SDT_V2 language for SDT_V3 probe. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 10 ++++++++-- 1 files changed, 8 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-03-27 4:01 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=20110327040110.1908.qmail@sourceware.org \ --to=fche@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).