public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-279-g031fda5 Date: Mon, 08 Nov 2010 19:52:00 -0000 [thread overview] Message-ID: <20101108195242.26099.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 031fda598f1616a7aa563132111ad5acf65599e6 (commit) via 7d62c1046ebecec03843c69d70acc41f08f481dc (commit) from 8358a79cf2a92e518a92c3c89eef53f880816239 (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 031fda598f1616a7aa563132111ad5acf65599e6 Author: Frank Ch. Eigler <fche@elastic.org> Date: Mon Nov 8 14:48:01 2010 -0500 PR11811: warn on missing unwind info with 'stap -d FOO' * unwind.c (unwind_frame): Demote common warnings to dbug_unwind messages. (unwind): Print a warning for unwind operations foiled by modules that did not have pre-uploaded unwind data. * buildrun.cxx (compile_pass): Check for exported __module_text_address. commit 7d62c1046ebecec03843c69d70acc41f08f481dc Author: Frank Ch. Eigler <fche@elastic.org> Date: Mon Nov 8 14:47:04 2010 -0500 fix accidental prefix '/' in abbreviated module name in backtraces * runtime/sym.c (_stp_snprint_addr): Use strrchr correctly. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 1 + runtime/sym.c | 4 +++- runtime/unwind.c | 34 ++++++++++++++++++++++++++++++---- 3 files changed, 34 insertions(+), 5 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-11-08 19:52 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=20101108195242.26099.qmail@sourceware.org \ --to=fche@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).