From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30757 invoked by alias); 21 Jan 2008 14:28:17 -0000 Received: (qmail 30199 invoked by uid 48); 21 Jan 2008 14:27:32 -0000 Date: Mon, 21 Jan 2008 14:28:00 -0000 Message-ID: <20080121142732.30198.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/msg00105.txt.bz2 ------- Additional Comments From srinivasa at in dot ibm dot com 2008-01-21 14:27 ------- Created an attachment (id=2207) --> (http://sourceware.org/bugzilla/attachment.cgi?id=2207&action=view) patch to solve the problem. Frank If user probes the kernel with below style, 1) probe kernel.statement("*@kernel/sched.c:1151") { 2) probe kernel.function("*@kernel/sched.c:1151") { there is chance the probe being at appropriate place( line number different than the user specified) and user is not informed about it. Thats one of the causes for the above problem. So above patch informs the user about new line number, in which it has put the probe. Please let me know your comments 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.