This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/13209] New: ubacktrace functions should only rely on vma tracker
- From: "mjw at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 21 Sep 2011 08:48:22 +0000
- Subject: [Bug runtime/13209] New: ubacktrace functions should only rely on vma tracker
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=13209
Bug #: 13209
Summary: ubacktrace functions should only rely on vma tracker
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: mjw@redhat.com
Classification: Unclassified
The current ubacktrace functions from tapset/ucontext-unwind.stp rely on both
/* pragma:vma */ and /* pragma:uprobes */ there are two issues with that.
1) Just relying on /* pragma:vma */ doesn't trigger the UTRACE check, so you
might accidentially use a function that needs the task finder vma tracker which
currently doesn't start (might be solved by taskfinder2 work, which shouldn't
rely on utrace).
2) ubacktrace doesn't actually need uprobes, it can unwind perfectly fine
without it. Except that IF uprobes is available it wants to use the
uprobe_get_pc() function to get around uretprobes. So the dependency is
inverted.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.