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-80-g4d51e8c Date: Wed, 07 Mar 2012 12:39:00 -0000 [thread overview] Message-ID: <20120307123939.26710.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 4d51e8ca64dd4f780781a1280bc7887acc822b33 (commit) from abcd27b8b950913a1c2588ef7f3dd0ec4bcd24dd (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 4d51e8ca64dd4f780781a1280bc7887acc822b33 Author: Mark Wielaard <mjw@redhat.com> Date: Wed Mar 7 13:35:56 2012 +0100 PR10622. Better workaround for GCC PR51410. Find external var DIE location. Some GCC versions would output duplicate external variables, one without a location attribute. If so, try to find the other if it exists in the same scope. This is a better solution than the previous fallback solution of just trying to get the address in the symbol table. That could result in picking the wrong external variable with the same name (but from a different CU). Add test case to show this works better. ----------------------------------------------------------------------- Summary of changes: dwflpp.cxx | 30 ++++++++++++++++ testsuite/systemtap.base/global_var.exp | 44 ++++++++++++++++++++++++ testsuite/systemtap.base/global_var.stp | 14 +++++++ testsuite/systemtap.base/global_var_distance.c | 4 ++ testsuite/systemtap.base/global_var_main.c | 30 ++++++++++++++++ testsuite/systemtap.base/global_var_speed.c | 4 ++ 6 files changed, 126 insertions(+), 0 deletions(-) create mode 100644 testsuite/systemtap.base/global_var.exp create mode 100644 testsuite/systemtap.base/global_var.stp create mode 100644 testsuite/systemtap.base/global_var_distance.c create mode 100644 testsuite/systemtap.base/global_var_main.c create mode 100644 testsuite/systemtap.base/global_var_speed.c hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-03-07 12:39 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=20120307123939.26710.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).