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.8-43-g73d53dd Date: Wed, 18 Jul 2012 22:14:00 -0000 [thread overview] Message-ID: <20120718221416.5755.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 73d53dd2213ce54a72db9b3bd029eb1f39760656 (commit) via e9a90eeef4d09e69fa8de9b9285dfd4bf1e22c7f (commit) from 9fdf787d2e57f77cfc4df0af8dfdadb8a5582847 (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 73d53dd2213ce54a72db9b3bd029eb1f39760656 Author: Josh Stone <jistone@redhat.com> Date: Wed Jul 18 15:05:59 2012 -0700 PR14369: Fix locating SDT w/ $vars, w/o debuginfo While current SDT can work without debuginfo, trying to use local $vars still requires a look into DWARF. If that debuginfo is broken or missing (as with asm probes), then we were reporting the probe entirely absent, instead of just the $var broken. This is undesirable if the $var access might have been optimized away, or was part of a @defined check that should just get 0. So now we try using debuginfo first, but if that fails go the direct route, and bad $vars can be resolved or error in the normal way. commit e9a90eeef4d09e69fa8de9b9285dfd4bf1e22c7f Author: Josh Stone <jistone@redhat.com> Date: Wed Jul 18 14:09:05 2012 -0700 PR13934: When SDT args don't use N@OP, split on spaces Assembly probes are not forced to use the N@OP form. In this case, N is inferred to be the native word size. Since we don't have a nice delimiter, just split it on spaces. SDT-asm authors then must not put any spaces in arguments, to avoid ambiguity. ----------------------------------------------------------------------- Summary of changes: tapsets.cxx | 43 ++++++++++++++++++++++---------- testsuite/systemtap.base/sdt_asm.stp | 6 ++++ testsuite/systemtap.base/sdt_misc.exp | 4 ++- 3 files changed, 38 insertions(+), 15 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-07-18 22:14 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=20120718221416.5755.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).