public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: brolley@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.4-6-g54b76f0 Date: Tue, 18 Jan 2011 19:41:00 -0000 [thread overview] Message-ID: <20110118194157.4743.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 54b76f09524ccb1ddcb62601f0db18cd81be3f72 (commit) from 557fc7ebe435fa97cb64620fbe26546128872acb (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 54b76f09524ccb1ddcb62601f0db18cd81be3f72 Author: Dave Brolley <brolley@redhat.com> Date: Tue Jan 18 14:39:08 2011 -0500 PR 11445: Check that assert_is_my_proc check is within all uprobes/utrace callback entry points Add comment explaining why a check for is_myproc() is not generated as a safety net for process.end probes and their variants. ----------------------------------------------------------------------- Summary of changes: tapset-utrace.cxx | 30 +++++++++++++++++++++--------- 1 files changed, 21 insertions(+), 9 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-01-18 19:41 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=20110118194157.4743.qmail@sourceware.org \ --to=brolley@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: linkBe 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).