[Bug translator/2475] New: Inlines don't match filenames correctly

["joshua dot i dot stone at intel dot com" <sourceware-bugzilla@sourceware.org>]

Consider a probe like this:
    probe kernel.inline("*@include/linux/mm.h")

The expected behavior is that this would probe all instances of inlines defined
within "include/linux/mm.h".  However, on i686 2.6.9-34.ELsmp, this actually
matches the following set:

  static struct kprobe dwarf_kprobe_4[17688]= {
    {.addr= (void *) 0xc0100566},
    {.addr= (void *) 0xc01005ac},
    {.addr= (void *) 0xc01005e1},
    {.addr= (void *) 0xc01005e6},
    {.addr= (void *) 0xc01005fc},
    ...
  };
 
  char const * dwarf_kprobe_0_location_names[17688] = {
    "kernel.inline(\"unlock_kernel@include/linux/smp_lock.h:53\")",
    "kernel.inline(\"execve@include/asm/unistd.h:437\")",
    "kernel.inline(\"get_current@include/asm/current.h:9\")",
    "kernel.inline(\"get_current@include/asm/current.h:9\")",
    "kernel.inline(\"fixup_cpu_present_map@init/main.c:761\")",
    ...
  };

At first glance I thought that this was all instances of inlines *used* within
the given file.  However, it seems suspicious that execve would be called from
within mm.h.  Closer inspection of the matching address (0xc01005ac) shows that
this probe point is the execve call within "run_init_process" in "init/main.c".
 In fact, all of the addresses from the exerpt above are from "init/main.c", and
have no obvious tie to "include/linux/mm.h".

So it appears that filename matching for inlines is completely broken...

See also this thread:
http://sources.redhat.com/ml/systemtap/2006-q1/msg00817.html

-- 
           Summary: Inlines don't match filenames correctly
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: joshua dot i dot stone at intel dot com


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

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