public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-81-gb1047bc
Date: Tue, 24 Jul 2012 13:14: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  b1047bc1aa2692f934bb34be4e7315db964d4391 (commit)
      from  3aeea85c567697379049fe1b69483e19c0adb45f (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 b1047bc1aa2692f934bb34be4e7315db964d4391
Author: David Smith <>
Date:   Tue Jul 24 08:13:56 2012 -0500

    Fixed PR13454 by updating pipe/pipe2 support in nd_syscalls.stp.
    * tapset/aux_syscalls.stp (_fildes_index_u): Renamed from _fildes_u() and
      reworked to return pipe fd values (instead of a string).
    * tapset/nd_syscalls2.stp: Updated nd_syscall.pipe probe alias to handle
    * testsuite/systemtap.syscall/nd_syscall.exp (syscall_kfails): Removed
      kfail for pipe test.


Summary of changes:
 tapset/aux_syscalls.stp                    |    8 +-
 tapset/nd_syscalls2.stp                    |   93 +++++++++++++++++++++-------
 testsuite/systemtap.syscall/nd_syscall.exp |   15 -----
 3 files changed, 74 insertions(+), 42 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-07-24 13:14 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).