public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: cmeek@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-248-g2eb99c6
Date: Thu, 22 Sep 2011 19:14:00 -0000 [thread overview]
Message-ID: <20110922191451.6162.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 2eb99c62e37e4f9b2b94479d686bfdc449a3ab7c (commit)
from e281908fcbcb10a848e109d23c3ca4f2d2ef0a40 (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 2eb99c62e37e4f9b2b94479d686bfdc449a3ab7c
Author: Chris Meek <cmeek@redhat.com>
Date: Thu Sep 22 15:04:32 2011 -0400
PR12221 cont'd: Added module suport for adding build id to hash
Now when you probe a module, the build ID of the module is
added to the script's hash.
dwflpp.cxx:
- Calls dwfl_getmodules in setup_kernel with a new callback
add_module_build_id_to_hash().
- Added add_module_build_id_to_hash() callback.
dwflpp.h:
- Added function declaration for above callback.
setupdwfl.cxx:
- Removed adding kernel build ID to session variable as new
callback handles that case as well.
-----------------------------------------------------------------------
Summary of changes:
dwflpp.cxx | 44 ++++++++++++++++++++++++++++++++++++++++++--
dwflpp.h | 9 ++++++++-
setupdwfl.cxx | 2 --
3 files changed, 50 insertions(+), 5 deletions(-)
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2011-09-22 19:14 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=20110922191451.6162.qmail@sourceware.org \
--to=cmeek@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).