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-240-gd0d7bd5 Date: Wed, 21 Sep 2011 10:41:00 -0000 [thread overview] Message-ID: <20110921104137.19065.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 d0d7bd5fd8ebe136c7afca43e157f04c1abed243 (commit) from 18418d34c087effe0c648ff4d75996855d38b46a (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 d0d7bd5fd8ebe136c7afca43e157f04c1abed243 Author: Mark Wielaard <mjw@redhat.com> Date: Wed Sep 21 12:38:24 2011 +0200 PR13210 vma/vdso tracking is broken testcase Add a generic testcase to see if we can track the vma from which a syscall was made. This might or might not come in through the vdso on the particular (compat) arch, but should always at least be able to get the vma name. Currently it fails some of the tests in different ways for different arches and/or kernel versions. ----------------------------------------------------------------------- Summary of changes: testsuite/systemtap.base/vma_vdso.c | 20 +++++++++++++ testsuite/systemtap.base/vma_vdso.exp | 49 +++++++++++++++++++++++++++++++++ testsuite/systemtap.base/vma_vdso.stp | 16 +++++++++++ 3 files changed, 85 insertions(+), 0 deletions(-) create mode 100644 testsuite/systemtap.base/vma_vdso.c create mode 100644 testsuite/systemtap.base/vma_vdso.exp create mode 100644 testsuite/systemtap.base/vma_vdso.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-09-21 10: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=20110921104137.19065.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).