public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
* [Bug tapsets/10499] New: Missing @file:line info from resolved probes
@ 2009-08-08  1:05 jistone at redhat dot com
  2009-08-08  1:10 ` [Bug tapsets/10499] " jistone at redhat dot com
  0 siblings, 1 reply; 2+ messages in thread
From: jistone at redhat dot com @ 2009-08-08  1:05 UTC (permalink / raw)
  To: systemtap

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug tapsets/10499] Missing @file:line info from resolved probes
  2009-08-08  1:05 [Bug tapsets/10499] New: Missing @file:line info from resolved probes jistone at redhat dot com
@ 2009-08-08  1:10 ` jistone at redhat dot com
  0 siblings, 0 replies; 2+ messages in thread
From: jistone at redhat dot com @ 2009-08-08  1:10 UTC (permalink / raw)
  To: systemtap


------- Additional Comments From jistone at redhat dot com  2009-08-08 01:10 -------
My debugging so far shows that dwarf_decl_file is returning NULL, because its
call to dwarf_attr(...DW_AT_decl_file...) returns NULL.  With readelf I can see
that the function does have DW_AT_decl_file/line.  I tried manually calling
dwarf_attr_integrate instead, and that found the file and line#.

It would probably be best if elfutils started using dwarf_attr_integrate in
dwarf_decl_file/line, but I'll see if there's a workaround possible in stap.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|systemtap at sources dot    |jistone at redhat dot com
                   |redhat dot com              |
             Status|NEW                         |ASSIGNED


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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2009-08-08  1:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-08-08  1:05 [Bug tapsets/10499] New: Missing @file:line info from resolved probes jistone at redhat dot com
2009-08-08  1:10 ` [Bug tapsets/10499] " jistone at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).