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.6-195-gac08441
Date: Fri, 09 Sep 2011 21:59:00 -0000	[thread overview]
Message-ID: <20110909215918.2222.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  ac08441a0456aa47c240aeeb725863c14165dce8 (commit)
       via  2a97f50bdda8562654b0fde3495a9cbc974c3519 (commit)
       via  6ac012fc4859c0d04e2718c4fda2eb84ba70b7a9 (commit)
      from  f400085292354d67a22af7205a4b918598da31df (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 ac08441a0456aa47c240aeeb725863c14165dce8
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Fri Sep 9 17:29:12 2011 -0400

    PR6503: actually allow module init/exit probes
    
    * dwflpp.cxx (dwflpp::blacklisted_p): Skip blacklist_section
      processing for modules, since we can (sometimes) probe their
      .init / .exit sections now.
    * runtime/staprun/staprun.c (send_relocation_modules): Hey, we
      only said "sometimes".  Preexisting modules lie in /sys/module/...
      about having their init stuff still in memory.  Skip those.

commit 2a97f50bdda8562654b0fde3495a9cbc974c3519
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Fri Sep 9 17:27:44 2011 -0400

    i18n: correct use of %# PRIx64 formatting
    
    During the i18n conversion, we ended up with several instances of 0x%#
    PRIx64 formatting directives, which duplicates the 0x.  This patch
    zaps those throughout.

commit 6ac012fc4859c0d04e2718c4fda2eb84ba70b7a9
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Fri Sep 9 15:05:28 2011 -0400

    PR6503: tweak blacklisting logic
    
    Previously, guru mode override for the blacklist only applied to the
    file/function blacklist.  With this rework, all blacklists may be
    bypassed in guru mode.

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

Summary of changes:
 dwflpp.cxx                |   65 +++++++++++++++++++++++----------------------
 runtime/staprun/staprun.c |    8 +++++-
 tapsets.cxx               |    6 ++--
 translate.cxx             |    4 +-
 4 files changed, 45 insertions(+), 38 deletions(-)


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


                 reply	other threads:[~2011-09-09 21:59 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=20110909215918.2222.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).