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-585-gbe6b4e2 Date: Mon, 12 Dec 2011 22:09:00 -0000 [thread overview] Message-ID: <20111212220900.7676.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 be6b4e27c36f15a77fa51dd920a5b24f5e57cc89 (commit) from efd3ff36c8aff15270d30bc9b315401eeb4f9c0b (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 be6b4e27c36f15a77fa51dd920a5b24f5e57cc89 Author: Mark Wielaard <mjw@redhat.com> Date: Mon Dec 12 22:52:18 2011 +0100 PR13467 Provide alternative testcase for pointer_array.exp. pointer_array.exp depends on indexing an array from a user pointer in kernel context. This doesn't work on s390x, which has separate user and kernel space addresses. kallsyms_expand_symbol.exp decodes the kallsyms table from kernel space using various array pointer manipulations. ----------------------------------------------------------------------- Summary of changes: .../systemtap.base/kallsyms_expand_symbol.exp | 12 ++++ .../systemtap.base/kallsyms_expand_symbol.stp | 54 ++++++++++++++++++++ testsuite/systemtap.base/pointer_array.exp | 3 + 3 files changed, 69 insertions(+), 0 deletions(-) create mode 100644 testsuite/systemtap.base/kallsyms_expand_symbol.exp create mode 100644 testsuite/systemtap.base/kallsyms_expand_symbol.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-12 22:09 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=20111212220900.7676.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).