public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-128-gbd5b25e
Date: Thu, 02 Aug 2012 17:36: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  bd5b25e1a7302785ec1609f9538dce13714f3f48 (commit)
      from  bb2626299dda0338ebe2e2ef2ff54940d351a237 (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 bd5b25e1a7302785ec1609f9538dce13714f3f48
Author: Josh Stone <>
Date:   Thu Aug 2 10:24:42 2012 -0700

    PR14378: Better @entry squashing in kprobe.function
    @entry is only valid in .return, but kprobe_var_expanding_visitor was
    expanding it blindly.  Then kprobe_derived_probe was failing its
    assertion that add_call_probe only happens with has_return.  So the test
    semko/entry04.stp was failing as it should, but rather ungracefully with
    an "Assertion `has_return' failed" abort.
    * tapsets.cxx (kprobe_var_expanding_visitor): Add a has_return member so
      we know our current context.
      (kprobe_var_expanding_visitor::visit_entry_op): Guard @entry expansion
      on has_return, the same way dwarf_var_expanding_visitor does.


Summary of changes:
 tapsets.cxx |   29 ++++++++++++++++++-----------
 1 files changed, 18 insertions(+), 11 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-08-02 17:36 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).