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-0.9.7-19-g975a582 Date: Mon, 27 Apr 2009 20:54:00 -0000 [thread overview] Message-ID: <20090427205429.6949.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 975a582b1274eb66088466a66a2eb2c3a70cf766 (commit) from 097e4a5b397b9e826453e01caa1f8169886128c5 (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 975a582b1274eb66088466a66a2eb2c3a70cf766 Author: David Smith <dsmith@redhat.com> Date: Mon Apr 27 15:53:21 2009 -0500 Fixed itrace on RHEL5 (PR10091). PR10091 fix. * runtime/itrace.c: Includes ptrace_compatibility.h. (usr_itrace_report_quiesce): Corrected return value for original version of utrace. * runtime/ptrace_compatibility.h: Defines arch_has_single_step() and arch_has_block_step() in terms of ARCH_HAS_SINGLE_STEP and ARCH_HAS_BLOCK_STEP. ----------------------------------------------------------------------- Summary of changes: runtime/itrace.c | 3 +- runtime/ptrace_compatibility.h | 50 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 52 insertions(+), 1 deletions(-) create mode 100644 runtime/ptrace_compatibility.h hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-04-27 20:54 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=20090427205429.6949.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).