This is the mail archive of the mailing list for the systemtap project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug runtime/14026] New: print_ubacktrace doesn't resolve the symbol name

             Bug #: 14026
           Summary: print_ubacktrace doesn't resolve the symbol name
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
    Classification: Unclassified

Created attachment 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());
        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:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]