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.3-266-g055e3b4
Date: Thu, 04 Nov 2010 02:36:00 -0000 [thread overview]
Message-ID: <20101104023559.13620.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 055e3b408aefb37a44c336af306f22c356fe321a (commit)
via ffde5a1bde318a27d237df7cc72c7dd062ccbfb8 (commit)
from 9fa0ffacffb59370d11c8a2947f8634c27370910 (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 055e3b408aefb37a44c336af306f22c356fe321a
Author: Josh Stone <jistone@redhat.com>
Date: Wed Nov 3 19:27:54 2010 -0700
Test that uprobes supports "rep ret"
We've made a special case in uprobes to support this sequence, since it
does occur in normal gcc output, so make sure of that. At the same
time, test that we reject other prefixes like "repnz ret", even though
we might be able to support them after more analysis.
commit ffde5a1bde318a27d237df7cc72c7dd062ccbfb8
Author: Josh Stone <jistone@redhat.com>
Date: Wed Nov 3 18:41:09 2010 -0700
uprobes_i386: backport check_legacy_prefix from uprobes2
Without this, we can't give "special" prefixed instructions the
treatment they deserve. (e.g. rep-ret)
-----------------------------------------------------------------------
Summary of changes:
runtime/uprobes/uprobes_i386.c | 61 +++++++++++++++++++++++++++------
testsuite/systemtap.base/rep_ret.c | 4 ++
testsuite/systemtap.base/rep_ret.exp | 61 ++++++++++++++++++++++++++++++++++
3 files changed, 115 insertions(+), 11 deletions(-)
create mode 100644 testsuite/systemtap.base/rep_ret.c
create mode 100644 testsuite/systemtap.base/rep_ret.exp
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2010-11-04 2: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:
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=20101104023559.13620.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).