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, pr10653-itrace-crashes, created. release-1.0-163-gbf26f2e Date: Sat, 21 Nov 2009 19:28:00 -0000 [thread overview] Message-ID: <20091121192759.31824.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, pr10653-itrace-crashes has been created at bf26f2eef2c262919e49db1d439bb7cee70aeee7 (commit) - Log ----------------------------------------------------------------- commit bf26f2eef2c262919e49db1d439bb7cee70aeee7 Author: Frank Ch. Eigler <fche@elastic.org> Date: Sat Nov 21 14:21:31 2009 -0500 PR10653: reorganize runtime/itrace.c Unfortunately it's not enough. * runtime/itrace.c (debug): Remove flag. Replace with -DDEBUG_ITRACE conditionals. (itrace_lock): Make a mutex. (usr_itrace_report_*): Rewrite. Include detach handling. (usr_itrace_init): Rewrite, merge create_itrace_info. (remove_usr_itrace_info): Remove. (usr_itrace_dtor_all): New function to start shutdown/detach, merge cleanup_usr_itrace. * tapset-itrace.cxx (emit_module_decls, _init): Rework startup and shutdown. * testsuite/systemtap.base/itrace.exp: Add -DDEBUG_foo parameters temporarily to stap invocations. Temporarily disable block-trace tests. * testsuite/lib/systemtap.exp (shutdown_server): Don't rm -rf "" (blank). ----------------------------------------------------------------------- hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-11-21 19:28 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=20091121192759.31824.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).