public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.7-167-geee30f4
Date: Tue, 26 May 2009 18:25:00 -0000	[thread overview]
Message-ID: <20090526182548.9772.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  eee30f40ac28c7090a269611fb1baea5c050c612 (commit)
      from  c9116e9980ad6e417697737f8d54a4a625811245 (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 eee30f40ac28c7090a269611fb1baea5c050c612
Author: Przemyslaw Pawelczyk <przemyslaw@pawelczyk.it>
Date:   Sat May 23 10:30:40 2009 +0200

    Fix nd_syscalls.stp for architectures using SYSCALL_WRAPPERS.
    
    Add kprobe.function("SyS_*") probe points to nd_syscall.* probe aliases.
    Analogue of commit 132c337c with two exceptions:
    - remove sufficiency of these new probe points (use '?' instead of '!'),
      because translator always considers them resolved,
    - make non-SyS probe points optional in probe aliases affected by
      syscall wrappers, because otherwise they will fail on such
      architectures.
    
    Signed-off-by: Josh Stone <jistone@redhat.com>

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

Summary of changes:
 tapset/nd_syscalls.stp |  873 +++++++++++++++++++++++++++++++-----------------
 1 files changed, 568 insertions(+), 305 deletions(-)


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


                 reply	other threads:[~2009-05-26 18:25 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=20090526182548.9772.qmail@sourceware.org \
    --to=jistone@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).