This is the mail archive of the systemtap@sourceware.org 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/10599] New: Always print module/map names for kernel/executable addresses


When the context tapset modname, [u]symname, [u]symdata or the backtrace
addresses mapped to symbol names (all this translates to _stp_symbol_print,
_stp_usymbol_print or _stp_symbol_snprint in runtime/syms.c) we only print the
module/library name associated with the address if we are currently tracking it.
Which means, we only print the module/library map name if we already have it in
our _stp_modules list.

Better vma tracking (bug #10228) means we get events for each loaded kernel
module and each mmap event (plus associated backing [shared library] file). We
should build a table of this so we can easily add support for at least printing
<module/map-name>+offset from the sym.c symbol_print functions.

Also slightly related, to print <vdso>+offset, bug #10080.

-- 
           Summary: Always print module/map names for kernel/executable
                    addresses
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: runtime
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: mjw at redhat dot com
 BugsThisDependsOn: 10080,10228


http://sourceware.org/bugzilla/show_bug.cgi?id=10599

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


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