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.4-359-g347d3d1 Date: Fri, 13 May 2011 17:20:00 -0000 [thread overview] Message-ID: <20110513172042.5345.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 347d3d15c261c362e94c6ab8ff5f9ec7abb73d52 (commit) from c934c3f53a182b14fd436cc7c99e6760ea81a719 (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 347d3d15c261c362e94c6ab8ff5f9ec7abb73d52 Author: Frank Ch. Eigler <fche@redhat.com> Date: Fri May 13 13:17:02 2011 -0400 shutdown hangs: offer option -DSTAP_OVERRIDE_STUCK_CONTEXT Sometimes stuff happens to probe handlers, and they refuse to clean up cleanly (resetting their contexts to non-busy state). This can cause module shutdowns to hang with a busy-waiting stapio. This patch lets a user override the infinite loop with -DSTAP_OVERRIDE_STUCK_CONTEXT to let the module be cleaned up. Without that set, at least the infinite loop is made to spin less tightly. * translate.cxx (c_unparser::emit_module_exit): Hang looser upon stuck contexts. ----------------------------------------------------------------------- Summary of changes: translate.cxx | 24 ++++++++++++++++++++++++ 1 files changed, 24 insertions(+), 0 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-05-13 17:20 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=20110513172042.5345.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).