public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-331-gcedf63f Date: Wed, 19 Oct 2011 15:01:00 -0000 [thread overview] Message-ID: <20111019150121.15063.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 cedf63f3a6bdcdf3196acc8b4e47ffca0e56ce97 (commit) from e04e95a488397d0fbf2740c3cfef989b56d7f80a (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 cedf63f3a6bdcdf3196acc8b4e47ffca0e56ce97 Author: David Smith <dsmith@redhat.com> Date: Wed Oct 19 10:00:45 2011 -0500 Fixed PR13158 by adding a staprun signal handler so modules don't remain. * runtime/staprun/staprun.c (term_signal_handler): New function. (setup_term_signals): Ditto. (insert_stap_module): Remembers if insert_module() worked. (main): Call setup_term_signals(). * testsuite/systemtap.base/rename_module.exp: Made test case more robust by waiting on output from all stap scripts. * testsuite/systemtap.base/pr13158.exp: New testcase. ----------------------------------------------------------------------- Summary of changes: runtime/staprun/staprun.c | 47 +++++++++++++- testsuite/systemtap.base/pr13158.exp | 55 ++++++++++++++++ testsuite/systemtap.base/rename_module.exp | 95 +++++++++++++++++---------- 3 files changed, 159 insertions(+), 38 deletions(-) create mode 100644 testsuite/systemtap.base/pr13158.exp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-10-19 15:01 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=20111019150121.15063.qmail@sourceware.org \ --to=dsmith@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).