This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/14026] New: print_ubacktrace doesn't resolve the symbol name
- From: "adrian.m.negreanu at intel dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Fri, 27 Apr 2012 10:00:31 +0000
- Subject: [Bug runtime/14026] New: print_ubacktrace doesn't resolve the symbol name
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14026
Bug #: 14026
Summary: print_ubacktrace doesn't resolve the symbol name
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap@sourceware.org
ReportedBy: adrian.m.negreanu@intel.com
Classification: Unclassified
Created attachment 6372
--> http://sourceware.org/bugzilla/attachment.cgi?id=6372
readelf -a on the debug file
On an android x86 target, I'm trying this script:
probe process("/system/bin/mksh").function("chvt_reinit") {
printf("%s: pid=%d\n", module_name(), pid());
printf("%s: ", module_name());
print_regs();
print_ubacktrace();
printf("%s: DONE\n",module_name());
}
The backtrace consists of only addresses.
I attached the output of stap + staprun,
readelf -a on the target executable and
of its .gnu_debuglink
and also the "readelf -debug-dump=frames target_executable".
One thing I noticed while trying to get more insight of what's happening,
was that if I define UNW_PC_FROM_RA to be 1, in -debug-dump=frames
the symbol is resolved but unwind() will only unwind the topmost frame.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.