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-1.8-113-g3d4557e
Date: Tue, 31 Jul 2012 02:58:00 -0000	[thread overview]
Message-ID: <20120731025759.21496.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  3d4557e23ab8b187950f4e600d756cd6005c2205 (commit)
       via  396db7018296def61cdad17934a67b877d2c73cc (commit)
       via  f705da87d68bdcd1b463c180c3ff778df107f617 (commit)
      from  f499dee559f3b13ba0a80c3013c02920e3233155 (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 3d4557e23ab8b187950f4e600d756cd6005c2205
Author: Josh Stone <jistone@redhat.com>
Date:   Mon Jul 30 19:56:18 2012 -0700

    Range-check _fildes_index_u and test it
    
    * tapset/linux/aux_syscalls.stp: Make sure the index is 0 or 1.
    * testsuite/buildok/aux_syscalls-embedded.stp: Test _fildes_index_u()
      rather than the old, removed _fildes_u().

commit 396db7018296def61cdad17934a67b877d2c73cc
Author: Josh Stone <jistone@redhat.com>
Date:   Mon Jul 30 19:34:43 2012 -0700

    PR14180: Move all syscall tapsets to linux/
    
    Moving basically all *syscall*.stp into tapset/linux/. These are all
    implemented from a kernel assumption, using either kernel.function or
    kprobe.function, and the supporting functions also assume that they're
    being called from a kernel environment.

commit f705da87d68bdcd1b463c180c3ff778df107f617
Author: Josh Stone <jistone@redhat.com>
Date:   Mon Jul 30 17:34:02 2012 -0700

    PR14180: Search for tapset in additional backend-specific paths
    
    We already search paths in many combinations of kernel version and arch.
    For each of these, search also in runtime-specific prefixes, "linux/..."
    for kernel mode, and "dyninst/..." for dyninst mode.  (And while we're
    at it, only do kernel versioning for kernel mode.)

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

Summary of changes:
 main.cxx                                    |   70 +++++++++++++++++----------
 tapset/{ => linux}/arm/aux_syscalls.stp     |    0
 tapset/{ => linux}/aux_syscalls.stp         |    2 +-
 tapset/{ => linux}/i386/aux_syscalls.stp    |    0
 tapset/{ => linux}/i386/nd_syscalls.stp     |    0
 tapset/{ => linux}/i386/syscalls.stp        |    0
 tapset/{ => linux}/ia64/aux_syscalls.stp    |    0
 tapset/{ => linux}/ia64/nd_syscalls.stp     |    0
 tapset/{ => linux}/ia64/syscalls.stp        |    0
 tapset/{ => linux}/nd_syscalls.stp          |    0
 tapset/{ => linux}/nd_syscalls2.stp         |    0
 tapset/{ => linux}/powerpc/aux_syscalls.stp |    0
 tapset/{ => linux}/powerpc/nd_syscalls.stp  |    0
 tapset/{ => linux}/powerpc/syscalls.stp     |    0
 tapset/{ => linux}/s390/aux_syscalls.stp    |    0
 tapset/{ => linux}/s390/nd_syscalls.stp     |    0
 tapset/{ => linux}/s390/syscalls.stp        |    0
 tapset/{ => linux}/syscalls.stp             |    0
 tapset/{ => linux}/syscalls2.stp            |    0
 tapset/{ => linux}/syscalls_cfg_trunc.stp   |    0
 tapset/{ => linux}/x86_64/aux_syscalls.stp  |    0
 tapset/{ => linux}/x86_64/nd_syscalls.stp   |    0
 tapset/{ => linux}/x86_64/syscalls.stp      |    0
 testsuite/buildok/aux_syscalls-embedded.stp |    2 +-
 24 files changed, 47 insertions(+), 27 deletions(-)
 rename tapset/{ => linux}/arm/aux_syscalls.stp (100%)
 rename tapset/{ => linux}/aux_syscalls.stp (99%)
 rename tapset/{ => linux}/i386/aux_syscalls.stp (100%)
 rename tapset/{ => linux}/i386/nd_syscalls.stp (100%)
 rename tapset/{ => linux}/i386/syscalls.stp (100%)
 rename tapset/{ => linux}/ia64/aux_syscalls.stp (100%)
 rename tapset/{ => linux}/ia64/nd_syscalls.stp (100%)
 rename tapset/{ => linux}/ia64/syscalls.stp (100%)
 rename tapset/{ => linux}/nd_syscalls.stp (100%)
 rename tapset/{ => linux}/nd_syscalls2.stp (100%)
 rename tapset/{ => linux}/powerpc/aux_syscalls.stp (100%)
 rename tapset/{ => linux}/powerpc/nd_syscalls.stp (100%)
 rename tapset/{ => linux}/powerpc/syscalls.stp (100%)
 rename tapset/{ => linux}/s390/aux_syscalls.stp (100%)
 rename tapset/{ => linux}/s390/nd_syscalls.stp (100%)
 rename tapset/{ => linux}/s390/syscalls.stp (100%)
 rename tapset/{ => linux}/syscalls.stp (100%)
 rename tapset/{ => linux}/syscalls2.stp (100%)
 rename tapset/{ => linux}/syscalls_cfg_trunc.stp (100%)
 rename tapset/{ => linux}/x86_64/aux_syscalls.stp (100%)
 rename tapset/{ => linux}/x86_64/nd_syscalls.stp (100%)
 rename tapset/{ => linux}/x86_64/syscalls.stp (100%)


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


                 reply	other threads:[~2012-07-31  2: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=20120731025759.21496.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).