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-251-g6109115 Date: Mon, 24 Sep 2012 23:24:00 -0000 [thread overview] Message-ID: <20120924232441.31745.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 6109115cda35fe9ced82dcd638f8e73008b757f5 (commit) from f4d8069ddf3a60224256acbbe105a534b7349ffd (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 6109115cda35fe9ced82dcd638f8e73008b757f5 Author: Josh Stone <jistone@redhat.com> Date: Mon Sep 24 16:15:55 2012 -0700 stapdyn: Enable end/error probes The dyninst exit hook runs too late for us to still call anything in the mutatee, so the systemtap_module_exit() call which should run all of the end/error probes wasn't happening. Now we use a destructor function in the mutatee, so our exit path always runs after main() returns or after an exit() call. Functions like _exit() are still problematic though. This now also makes a distinction between initializing process-local vs. session resources, so we are more ready for operating with multiple mutatees at once. See dyninst/runtime.h for design comments. ----------------------------------------------------------------------- Summary of changes: runtime/dyninst/runtime.h | 58 +++++++++++++++++++++++++++++++++++++++++---- stapdyn/stapdyn.cxx | 13 ++++------ 2 files changed, 58 insertions(+), 13 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-09-24 23:24 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=20120924232441.31745.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).