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-48-gf450a7e Date: Tue, 17 Aug 2010 19:58:00 -0000 [thread overview] Message-ID: <20100817195839.12390.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 f450a7e3b805a066df1a634e231b73c22b7229b8 (commit) from 8dc503b652ce152a4cde60ea2ba3faebb461271d (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 f450a7e3b805a066df1a634e231b73c22b7229b8 Author: Josh Stone <jistone@redhat.com> Date: Tue Aug 17 12:42:49 2010 -0700 Support DWARF4 linkage names With -gdwarf-4, gcc outputs DW_AT_linkage_name instead of DW_AT_MIPS_linkage_name. Semantics are unchanged. * dwarf_wrappers.h (dwarf_linkage_name): New, retrieves the linkage_name by either the old or new attribute value. * dwflpp.cxx (dwflpp::iterate_over_functions): Use dwarf_linkage_name. (dwflpp::vardie_from_symtable): Ditto. * tapsets.cxx (dwarf_query::add_probe_point): Ditto. ----------------------------------------------------------------------- Summary of changes: dwarf_wrappers.h | 17 +++++++++++++++++ dwflpp.cxx | 12 ++---------- tapsets.cxx | 4 +--- 3 files changed, 20 insertions(+), 13 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-08-17 19:58 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=20100817195839.12390.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).