Bug 4397 - should tolerate source file names with /long/unexpected/prefix/driver/foo.c
Summary: should tolerate source file names with /long/unexpected/prefix/driver/foo.c
Status: RESOLVED DUPLICATE of bug 5049
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-19 18:15 UTC by Martin Hunt
Modified: 2007-10-15 19:44 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Hunt 2007-04-19 18:15:34 UTC
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
Comment 1 Frank Ch. Eigler 2007-04-19 18:31:52 UTC
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.
Comment 2 Martin Hunt 2007-04-19 18:47:43 UTC
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.
Comment 3 Frank Ch. Eigler 2007-10-15 19:44:27 UTC

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