[Bug tapsets/10499] New: Missing @file:line info from resolved probes

["jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

I've noticed that sometimes stap doesn't report the @file:line info on resolved
function probes.  This seems to be more common with class methods.  For example:

$ ./run-stap -l 'process("./stap").function("visit_target_symbol")' -v
Pass 1: parsed user script and 59 library script(s) in 120usr/30sys/143real ms.
process("/home/jistone/systemtap/build/stap").function("visit_target_symbol")
Pass 2: analyzed script: 8 probe(s), 0 function(s), 0 embed(s), 0 global(s) in
40usr/10sys/51real ms.

It resolved to 8 different probes, all in different visitor classes, but we
can't tell that because there's no source context.

-- 
           Summary: Missing @file:line info from resolved probes
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tapsets
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: jistone at redhat dot com


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

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