public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-518-ge2d98c6
Date: Tue, 29 Nov 2011 21:52:00 -0000	[thread overview]
Message-ID: <> (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  e2d98c60dcbb1dee319e9bd5c5fdc3a7198fd636 (commit)
      from  72dd064de16fe530bd16ba4622dcb16effbfc361 (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 e2d98c60dcbb1dee319e9bd5c5fdc3a7198fd636
Author: David Smith <>
Date:   Tue Nov 29 15:52:13 2011 -0600

    Added individual tests for and function.return probes.
    * testsuite/systemtap.base/uprobes.exp: Added sub-tests that check .call
      and .return probes individually.
    * testsuite/systemtap.base/uprobes_call.stp: New file.
    * testsuite/systemtap.base/uprobes_return.stp: New file.


Summary of changes:
 testsuite/systemtap.base/uprobes.exp        |   57 ++++++++++++++++++--------
 testsuite/systemtap.base/uprobes_call.stp   |    2 +
 testsuite/systemtap.base/uprobes_return.stp |    2 +
 3 files changed, 43 insertions(+), 18 deletions(-)
 create mode 100644 testsuite/systemtap.base/uprobes_call.stp
 create mode 100644 testsuite/systemtap.base/uprobes_return.stp

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2011-11-29 21:52 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be 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).