public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-133-gc0456b6
Date: Fri, 23 Mar 2012 20:52:00 -0000	[thread overview]
Message-ID: <> (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  c0456b6fda16307070e0896d3cca86f523214a5e (commit)
      from  ca73974d84f94065dbabce2a2044d17a83bade57 (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 c0456b6fda16307070e0896d3cca86f523214a5e
Author: David Smith <>
Date:   Fri Mar 23 15:52:01 2012 -0500

    Improve build-id checking when the task we're interested in isn't 'current'.
    * translate.cxx (emit_module_init): Moved include files to
    * runtime/runtime.h: Moved includes here from translate.cxx.  Rearranged
      order a bit, to allow use of __access_process_vm() earlier.
    * runtime/sym.c (_stp_build_id_check): Instead of passing in a flag to
      indicate build-id checking a user module, instead pass a task_struct
      pointer in.  If the task_struct pointer isn't 'current', use
      __access_process_vm() to read data.
      (_stp_module_check): Update _stp_build_id_check() call.
      (_stp_kmodule_check): Ditto.
      (_stp_usermodule_check): Ditto.
    * runtime/vma.c (_stp_vma_match_vdso): If the task we're trying to match
      isn't 'current', use __access_process_vm() to read data.


Summary of changes:
 runtime/runtime.h |   38 +++++++++++++++++++++++++-------------
 runtime/sym.c     |   52 ++++++++++++++++++++++++++++++----------------------
 runtime/vma.c     |   12 ++++++++++--
 translate.cxx     |   17 -----------------
 4 files changed, 65 insertions(+), 54 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-03-23 20:52 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).