public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: dsmith@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-197-g3fb24a3
Date: Fri, 17 Aug 2012 18:32:00 -0000 [thread overview]
Message-ID: <20120817183206.9354.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 3fb24a3676d8a6e35bd9e5d1e30ad95fc5281a32 (commit)
from dec33462a7fedd49ddce65f83f132f54ff3e0ff4 (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 3fb24a3676d8a6e35bd9e5d1e30ad95fc5281a32
Author: David Smith <dsmith@redhat.com>
Date: Fri Aug 17 13:31:24 2012 -0500
Fixed PR14463 by changing error handling of utrace_control().
* runtime/stp_utrace.c (utrace_barrier): Add a 'might_sleep()' call since
it calls schedule_timeout_interruptible(), which sleeps.
* runtime/linux/task_finder2.c (__stp_utrace_attach): Ignore
EINPROGRESS errors from utrace_control() when passed UTRACE_STOP, since
that just means the task hasn't stopped yet.
* runtime/linux/task_finder.c (__stp_utrace_attach_flags): Ditto.
-----------------------------------------------------------------------
Summary of changes:
runtime/linux/task_finder.c | 15 +++++++--------
runtime/linux/task_finder2.c | 18 ++++++++----------
runtime/stp_utrace.c | 3 +++
3 files changed, 18 insertions(+), 18 deletions(-)
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2012-08-17 18:32 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=20120817183206.9354.qmail@sourceware.org \
--to=dsmith@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).