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-0.9-74-gc12d974
Date: Sat, 07 Mar 2009 22:12:00 -0000	[thread overview]
Message-ID: <20090307221227.25490.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  c12d974f4ad369f8d7585f2f07713dae3654b3fb (commit)
       via  944e2486c1bc490ead36fca86131b2a38416067d (commit)
      from  bc9a523d505c604c187dd2e81be1e24ec877d1af (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 c12d974f4ad369f8d7585f2f07713dae3654b3fb
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Sat Mar 7 17:00:54 2009 -0500

    PR9930: reentrancy debugging
    
     If stap is run with "-t -DDEBUG_REENTRANCY", additional warnings will
     be printed for every reentrancy event, including the probe points of
     the resident and interloper probes.
    
     * tapsets.cxx (common_probe_entryfn_prologue): Add "new_pp" argument,
     update all callers.  Print reentrancy details if needed.

commit 944e2486c1bc490ead36fca86131b2a38416067d
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Sat Mar 7 16:42:57 2009 -0500

    Add placeholder for new news

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

Summary of changes:
 NEWS        |    2 +
 tapsets.cxx |   73 ++++++++++++++++++++++++++++------------------------------
 2 files changed, 37 insertions(+), 38 deletions(-)


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


                 reply	other threads:[~2009-03-07 22: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=20090307221227.25490.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).