public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: mark@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-564-g7fbefbb Date: Fri, 09 Dec 2011 14:26:00 -0000 [thread overview] Message-ID: <20111209142641.27976.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 7fbefbb8e5d2651495310bd69a6526fef283ad7a (commit) from 972ea1e0125b9c3c20cd021c7d1ef17d7d215d82 (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 7fbefbb8e5d2651495310bd69a6526fef283ad7a Author: Mark Wielaard <mjw@redhat.com> Date: Fri Dec 9 15:24:03 2011 +0100 Move __stp_tf_vma_map check from commit 972ea1 to stap_find_vma_map_info(). Commit 972ea1 misapplied the check to stap_add_vma_map_info. This can never be called when the vma tracker hasn't been initialized. But stap_find_vma_map_info[_user] potentially could be called. And so this function needs to check that sure__stp_tf_vma_map is initialized. ----------------------------------------------------------------------- Summary of changes: runtime/task_finder_vma.c | 13 ++++++++----- 1 files changed, 8 insertions(+), 5 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-09 14:26 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=20111209142641.27976.qmail@sourceware.org \ --to=mark@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).