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-232-g464379b
Date: Mon, 19 Sep 2011 18:28:00 -0000	[thread overview]
Message-ID: <20110919182835.21082.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  464379bbacf6c9a3f007cb81e5e8cfdfb8617bd2 (commit)
      from  98d05dce9a9304ea17b5ffd4b9bb19837e92b44b (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 464379bbacf6c9a3f007cb81e5e8cfdfb8617bd2
Author: Frank Ch. Eigler <fche@redhat.com>
Date:   Mon Sep 19 14:25:43 2011 -0400

    PR13200: skip prologue searching for *.function(ADDR).return probes
    
    Prologue searching has to be suppressed for all kretprobes/uretprobes
    address calculations, or else the *retprobes facility can overwrite
    valid stack frame data instead of return addresses.
    
    * tapsets.cxx (query_addr, query_func_info): Perform prologue analysis
      but verbosely ignore results, for .return probes.

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

Summary of changes:
 tapsets.cxx |   19 +++++++++++++++++--
 1 files changed, 17 insertions(+), 2 deletions(-)


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


                 reply	other threads:[~2011-09-19 18:28 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=20110919182835.21082.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).