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-59-g8c67c33 Date: Thu, 19 Aug 2010 23:26:00 -0000 [thread overview] Message-ID: <20100819232658.4831.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 8c67c3379b9be66d977a70e09f121997f5d85a19 (commit) from fef0686c2455144bc47e69d41a4615bf395ecc98 (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 8c67c3379b9be66d977a70e09f121997f5d85a19 Author: Josh Stone <jistone@redhat.com> Date: Wed Aug 18 16:23:29 2010 -0700 PR11911: Include in -L vars which are partially available Mostly this is for aggregate types, like a struct type where we can't translate $foo, but $foo->bar works just fine. So instead of seeing if translation works without error, we now look for location info ourselves. We list all $vars which are present at this address, even if not "fully" available. This also adds verbosity on errors, for PR11910. * tapsets.cxx (dwarf_derived_probe::saveargs): Check for locations manually instead of trying translation. * testsuite/semok/bz11911.stp: New test adapted from Roland. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 110 +++++++++++++++++++++++++++++-------------- testsuite/semok/bz11911.stp | 24 +++++++++ 2 files changed, 99 insertions(+), 35 deletions(-) create mode 100755 testsuite/semok/bz11911.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-08-19 23:26 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=20100819232658.4831.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).