[Bug translator/4397] New: problem with probes on files with self-built kernel

[Bug translator/4397] New: problem with probes on files with self-built kernel

[hunt at redhat dot com]

I built and installed 2.6.20.7.

Testsuite all runs fine except current.stp which dies on this:
semantic error: no match for probe point while resolving probe point
kernel.function("*@kernel/sched.c").call

Changing that to kernel.function("*").call, I see lots on enabled probes in sched.c

probe
sys_sched_setaffinity@/data/hunt/linux/linux-2.6.20.7-utt/kernel/sched.c:4485
kernel section=.text pc=0xc0422e6f
probe sched_idle_next@/data/hunt/linux/linux-2.6.20.7-utt/kernel/sched.c:5234
kernel section=.text pc=0xc0422eb0
probe current_sched_time@/data/hunt/linux/linux-2.6.20.7-utt/kernel/sched.c:3027
kernel section=.text pc=0xc0422f30

-- 
           Summary: problem with probes on files with self-built kernel
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: translator
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: hunt at redhat dot com


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

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

[Bug translator/4397] problem with probes on files with self-built kernel

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2007-04-19 18:31 -------
The issue here is that the compilation unit name "kernel/sched.c"
pattern does not match the full path compiled on your tree.  Plus
our globbing function does not permit full-path patterns like
"**/kernel/sched.c".  It's not obvious what to do here.

-- 


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

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

[Bug translator/4397] problem with probes on files with self-built kernel

[hunt at redhat dot com]

------- Additional Comments From hunt at redhat dot com  2007-04-19 18:47 -------
I wonder how common this is. I expect if I had built in my source tree instead
of into a separate object directory things would work normally. I will try that.

-- 


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

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

[Bug translator/4397] should tolerate source file names with /long/unexpected/prefix/driver/foo.c

[fche at redhat dot com]

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|problem with probes on files|should tolerate source file
                   |with self-built kernel      |names with
                   |                            |/long/unexpected/prefix/driv
                   |                            |er/foo.c


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

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

[Bug translator/4397] should tolerate source file names with /long/unexpected/prefix/driver/foo.c

[fche at redhat dot com]

------- Additional Comments From fche at redhat dot com  2007-10-15 19:44 -------


*** This bug has been marked as a duplicate of 5049 ***

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE


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

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