public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: moore@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-370-g5e562a6
Date: Wed, 16 Dec 2009 14:07:00 -0000	[thread overview]
Message-ID: <20091216140720.10958.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  5e562a69a5432566c6ae78344ae51b80ced7f15b (commit)
      from  39a3e39706a18dbf3698b52fc1cc7532d94078e8 (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 5e562a69a5432566c6ae78344ae51b80ced7f15b
Author: Tim Moore <timoore@redhat.com>
Date:   Wed Dec 16 12:00:55 2009 +0100

    set the IP in return probes to the returned-to instruction
    
    It's easily available in kretprobes and uretprobes and is consistent
    with the rest of the program state.
    
    * translate.cxx (emit_common_header) : add uretprobe_instance to context.
    * tapsets.cxx (common_probe_entryfn_prologue): Initialize ri in
      context to 0.
      (dwarf_derived_probe_group::emit_module_decls): Change IP to return
      address in kretprobes.
      (uprobe_derived_probe_group::emit_module_decls): enter_uretprobe_probe:
      set ri (uretprobe_instance) in context. Change IP to return
      address in uretprobes. Don't emit uprobe include and #define
    * runtime/runtime.h : Add includes and #define for uprobes.
    * runtime/stack.c (_stp_stack_print, _stp_stack_snprint): Add extra
      argument for uretprobe_instance.
    * tapset/context-unwind.stp (print_backtrace, backtrace): Pass NULL
      for uretprobe_instance to _stp_stack_print.
    * tapset/ucontext-unwind.stp (print_ubacktrace, ubacktrace): pass
      uretprobe_instance to _stp_stack_print
    * testsuite/systemtap.context/uprobe_uaddr.exp : new test for uaddr in
      function probes
    * testsuite/systemtap.context/uprobe_uaddr.stp : new file

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

Summary of changes:
 runtime/runtime.h                            |   11 +++++
 runtime/stack.c                              |   11 ++++-
 tapset/context-unwind.stp                    |    4 +-
 tapset/ucontext-unwind.stp                   |    4 +-
 tapsets.cxx                                  |   23 +++++-----
 testsuite/systemtap.context/uprobe_uaddr.exp |   58 ++++++++++++++++++++++++++
 testsuite/systemtap.context/uprobe_uaddr.stp |   24 +++++++++++
 translate.cxx                                |    1 +
 8 files changed, 117 insertions(+), 19 deletions(-)
 create mode 100644 testsuite/systemtap.context/uprobe_uaddr.exp
 create mode 100644 testsuite/systemtap.context/uprobe_uaddr.stp


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


                 reply	other threads:[~2009-12-16 14:07 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=20091216140720.10958.qmail@sourceware.org \
    --to=moore@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).