[Bug runtime/4904] hard to use statement probes for line-by-line tracing

["srinivasa at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From srinivasa at in dot ibm dot com  2008-01-22 10:11 -------
Frank 
 I was using this script, 
   probe kernel.statement("*@kernel/sched.c:100"), which points to a comment 
statement in sched.c, but systemtap was putting probe point to first function 
in that file at line number 122. This is good.  What is missing here, a warning 
which tells user that "Real probe point in source file(line number) is 
different".


=================================
[root@llm27lp1 src]# ./stap -p2 /root/b.stp
Line number 122 is probed instead of 100 in file 'kernel/sched.c'
# global embedded code
%{
#include <linux/time.h>
%}
# functions
cpu:long ()
gettimeofday_ns:long ()
gettimeofday_us:long ()
# probes
kernel.statement("sg_div_cpu_power@kernel/sched.c:100") /* pc=0x69090 */ /* <- 
kernel.statement("sg_div_cpu_power@kernel/sched.c:100") */
===========================

Thanks
 Srinivasa DS

-- 


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

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