public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-388-g8cc799a
Date: Wed, 30 Jun 2010 23:50:00 -0000 [thread overview]
Message-ID: <20100630235055.9013.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 8cc799a5dece8e2358037a147458a5f9c3d9727a (commit)
from 23fdba572eb9e568312378bd2b560f3ba1a791d9 (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 8cc799a5dece8e2358037a147458a5f9c3d9727a
Author: Josh Stone <jistone@redhat.com>
Date: Wed Jun 30 16:39:11 2010 -0700
PR10943: support @entry saving in .return probes
* staptree.h (struct entry_op): New.
* parse.cxx (parse_entry_op): Parse @entry into an entry_op.
* elaborate.cxx, staptree.cxx, translate.cxx: Add entry_op boilerplate.
* tapsets.cxx (dwarf_var_expanding_visitor::visit_entry_op): New, save
operand value using gen_mapped_saved_return.
(dwarf_var_expanding_visitor::gen_mapped_saved_return): Use a new flag
to see if the tid is already saved, because the add_block may have
been created by gen_kretprobe_saved_return instead.
* NEWS, stapprobes.3stap: Document it.
* testsuite/sem*/entry*.stp: Test it.
-----------------------------------------------------------------------
Summary of changes:
NEWS | 4 +++
elaborate.cxx | 7 ++++++
elaborate.h | 1 +
parse.cxx | 18 ++++++++++++++++-
stapprobes.3stap | 10 +++++++++
staptree.cxx | 45 +++++++++++++++++++++++++++++++++++++++++++
staptree.h | 14 +++++++++++++
tapsets.cxx | 31 +++++++++++++++++++++++++++++
testsuite/semko/entry01.stp | 8 +++++++
testsuite/semko/entry02.stp | 8 +++++++
testsuite/semko/entry03.stp | 8 +++++++
testsuite/semok/entry01.stp | 10 +++++++++
testsuite/semok/entry02.stp | 10 +++++++++
testsuite/semok/entry03.stp | 20 +++++++++++++++++++
translate.cxx | 8 +++++++
15 files changed, 201 insertions(+), 1 deletions(-)
create mode 100755 testsuite/semko/entry01.stp
create mode 100755 testsuite/semko/entry02.stp
create mode 100755 testsuite/semko/entry03.stp
create mode 100755 testsuite/semok/entry01.stp
create mode 100755 testsuite/semok/entry02.stp
create mode 100755 testsuite/semok/entry03.stp
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2010-06-30 23:50 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=20100630235055.9013.qmail@sourceware.org \
--to=jistone@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).