public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-205-ga794dbe
Date: Fri, 04 Jun 2010 21:12:00 -0000	[thread overview]
Message-ID: <20100604211228.14223.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  a794dbeb46b799de52ee118bf1d18aee4a9c5db6 (commit)
      from  a8fcf687bc8f8763ac8669c40eaf74396b0dd73e (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 a794dbeb46b799de52ee118bf1d18aee4a9c5db6
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Jun 4 17:01:52 2010 -0400

    PR11095: support process(). **provider()** .mark()
    
    For STAP_SDT_V2 only for now.
    
    * NEWS, stapprobes.3stap.in: Mention it.
    * Makefile.am (stap_CPPFLAGS): Use -DSTAP_SDT_V2.
    * dtrace.in: Preserve provider name, though squash it for STAP_SDT_V1.
    * includes/sys/sdt.h: Likewise.
    * tapsets.cxx (register_patterns): Accept .provider() probe point piece.
      (sdt_*_var_expanding_visotor): Store it.
      (sdt_query::*): Extend for provider matching, new magic codes.
    * testsuite/systemtap.base/sdt_misc.exp: Use more formal interfaces
      to semaphores.

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

Summary of changes:
 Makefile.am                           |    2 +-
 Makefile.in                           |    3 +-
 NEWS                                  |   14 ++-
 dtrace.in                             |   17 +++-
 includes/sys/sdt.h                    |  192 +++++++++++++++++---------------
 stapprobes.3stap.in                   |   18 ++--
 tapsets.cxx                           |  118 +++++++++++++++-----
 testsuite/systemtap.base/sdt_misc.exp |   14 ++--
 8 files changed, 232 insertions(+), 146 deletions(-)


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


                 reply	other threads:[~2010-06-04 21:12 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=20100604211228.14223.qmail@sourceware.org \
    --to=fche@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).