This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/13210] vdso runtime tracking is broken
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 21 Sep 2011 10:47:31 +0000
- Subject: [Bug runtime/13210] vdso runtime tracking is broken
- Auto-submitted: auto-generated
- References: <bug-13210-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13210
--- Comment #1 from Mark Wielaard <mjw at redhat dot com> 2011-09-21 10:47:31 UTC ---
Added a testcase for this that uses umodname(uaddr()) to check whether the vma
tracker at least got the name (of either the vdso or another vma that initiated
the syscall).
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.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.