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.0-79-ge34d5d1 Date: Thu, 08 Oct 2009 21:38:00 -0000 [thread overview] Message-ID: <20091008213800.22287.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 e34d5d1388d3c7817313685e3f7424ffc158474f (commit) from 1beb508976ba5a79758ffe6e174f47a64225f449 (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 e34d5d1388d3c7817313685e3f7424ffc158474f Author: Frank Ch. Eigler <fche@elastic.org> Date: Thu Oct 8 17:36:36 2009 -0400 PR10746: improve error message on utrace-less kernels * tapset-itrace.exp (itrace_derived_probe ctor): Fail if !CONFIG_UTRACE. * tapset-utrace.exp (utrace_derived_probe ctor): Fail if !CONFIG_UTRACE. * tapsets.cxx (dwarf_builder::build): Fail process.* if !CONFIG_UTRACE. * testsuite/semko/utrace.stp: New test. ----------------------------------------------------------------------- Summary of changes: tapset-itrace.cxx | 2 ++ tapset-utrace.cxx | 3 +++ tapsets.cxx | 3 +++ testsuite/semko/utrace.stp | 3 +++ 4 files changed, 11 insertions(+), 0 deletions(-) create mode 100755 testsuite/semko/utrace.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-10-08 21:38 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=20091008213800.22287.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).