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-1.8-52-gbbd3b1b
Date: Fri, 20 Jul 2012 18:58:00 -0000	[thread overview]
Message-ID: <20120720185815.21942.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  bbd3b1bb164e51aec7694d26e85f72dafdffbc9c (commit)
      from  4a2970a33fdd9fee72e4bad775d18ae806d2c949 (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 bbd3b1bb164e51aec7694d26e85f72dafdffbc9c
Author: David Smith <dsmith@redhat.com>
Date:   Fri Jul 20 13:57:48 2012 -0500

    Fixed PR13451 by updating dup2/dup3 support in nd_syscalls.stp.
    
    * tapset/nd_syscalls.stp: Updated dup2/dup3 probe aliases.
    * tapset/registers.stp: Removed dummy function and added
      __asmlinkage_int_arg(), needed by nd_syscall.return functions to grab
      entry values when asmlinkage() is needed.
    * testsuite/systemtap.syscall/nd_syscall.exp (syscall_kfails): Removed dup
      kfail.

-----------------------------------------------------------------------

Summary of changes:
 tapset/nd_syscalls.stp                     |  108 ++++++++++++++++++++++++++--
 tapset/registers.stp                       |   13 +++-
 testsuite/systemtap.syscall/nd_syscall.exp |    1 -
 3 files changed, 113 insertions(+), 9 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2012-07-20 18:58 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=20120720185815.21942.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: 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).