From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13122 invoked by alias); 22 Jan 2008 10:12:01 -0000 Received: (qmail 12960 invoked by uid 48); 22 Jan 2008 10:11:14 -0000 Date: Tue, 22 Jan 2008 10:12:00 -0000 Message-ID: <20080122101114.12958.qmail@sourceware.org> From: "srinivasa at in dot ibm dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070808060340.4904.bharata@linux.vnet.ibm.com> References: <20070808060340.4904.bharata@linux.vnet.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/4904] hard to use statement probes for line-by-line tracing X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2008-q1/txt/msg00124.txt.bz2 ------- 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 %} # 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.