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-98-g3965e10 Date: Fri, 09 Mar 2012 15:04:00 -0000 [thread overview] Message-ID: <20120309150439.15935.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 3965e105b73e196ec4f9b15c0b192c59bb14a2f8 (commit) via 3d9381fc814162b914288d45ff52017bf0a83fb4 (commit) from 4bf09a21457027eb511bb16a9355d6e17a93ae5f (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 3965e105b73e196ec4f9b15c0b192c59bb14a2f8 Author: Mark Wielaard <mjw@redhat.com> Date: Fri Mar 9 15:57:31 2012 +0100 Global vars don't need (cannot use) frame base in location descriptor. And so they also don't need cfa_ops (CFI) to calculate the frame base. commit 3d9381fc814162b914288d45ff52017bf0a83fb4 Author: Mark Wielaard <mjw@redhat.com> Date: Fri Mar 9 15:19:12 2012 +0100 Update verbose log and semantic exception messages for local vs global vars. Global @vars (with @cu/src_name.c) have a fixed scope/CU and don't depend on location/PC. Make that clean in verbose log and semantic error messages. ----------------------------------------------------------------------- Summary of changes: dwflpp.cxx | 62 ++++++++++++++++++++++++++++++++++++++++++++++++----------- 1 files changed, 50 insertions(+), 12 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-03-09 15:04 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=20120309150439.15935.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).