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-634-g76d01f3
Date: Tue, 20 Dec 2011 20:55:00 -0000	[thread overview]
Message-ID: <20111220205522.16132.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  76d01f364821ab3d76219c5a37422ae85a6e6d31 (commit)
       via  14fe042f4935946ad8ed68984a7ffc83b00634e3 (commit)
      from  5640998862caa69c671d155615b6a57d2a366d81 (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 76d01f364821ab3d76219c5a37422ae85a6e6d31
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Tue Dec 20 15:52:27 2011 -0500

    modinfo: also apply to uprobes.ko
    
    Continue commit 633e5ca70 with respect to a self-built uprobes.ko,
    in that --modinfo k=V values should be propagated there too.

commit 14fe042f4935946ad8ed68984a7ffc83b00634e3
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Tue Dec 20 15:49:35 2011 -0500

    PR13489: don't confuse staprun's "is uprobes in the kernel?" logic
    
    After recent commits associated with PR13489, a stap module may
    include a few symbols named kallsyms_*, specifically
    *unregister_uprobe.  This confused staprun's simpleminded grep on
    /proc/kallsyms to guess that uprobes per se was in the kernel, even
    though it was just some peer stap module.  So now grep for a more
    picky regexp, including all-important whitespace.
    
    * runtime/staprun/staprun.c (enable_uprobes): Look for
      " unregister_uprobe\t" instead of "unregister_uprobe".

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

Summary of changes:
 buildrun.cxx              |   11 +++++++++++
 runtime/staprun/staprun.c |    3 ++-
 2 files changed, 13 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2011-12-20 20:55 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=20111220205522.16132.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).