public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: scox@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-272-g155bb07
Date: Sat, 06 Nov 2010 03:06:00 -0000	[thread overview]
Message-ID: <20101106030604.27200.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  155bb07a5bfdd16b112870f7064f012970b7fbd9 (commit)
      from  d62c77361a7adaa87479b4930a9cd1e5889abb9d (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 155bb07a5bfdd16b112870f7064f012970b7fbd9
Author: Stan Cox <scox@redhat.com>
Date:   Fri Nov 5 23:02:39 2010 -0400

    Add build id support for user modules.
    
    * sym.c (_stp_build_id_check): New.  Moved the build id check code from
     _stp_module_check and changed...
    (_stp_module_check): to use it.
    (_stp_usermodule_check): New.  This is called from the
    task manager callback stap_uprobe_change_plus for the process found and
    mmap found cases.
    
    * translate.cxx (dump_unwindsyms): Don't stop if it isn't a kernel module.
    Set build_id_vaddr for user modules.  Output module->build_id_offset as an
    absolute address.
    
    * uprobes-common.c (stap_uprobe_change_plus): Call _stp_usermodule_check.

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

Summary of changes:
 runtime/sym.c            |  132 +++++++++++++++++++++++++++++++---------------
 runtime/uprobes-common.c |    2 +
 translate.cxx            |   18 ++++---
 3 files changed, 103 insertions(+), 49 deletions(-)


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


                 reply	other threads:[~2010-11-06  3:06 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=20101106030604.27200.qmail@sourceware.org \
    --to=scox@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).