This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug runtime/4904] hard to use statement probes for line-by-line tracing
- From: "srinivasa at in dot ibm dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 21 Jan 2008 14:27:32 -0000
- Subject: [Bug runtime/4904] hard to use statement probes for line-by-line tracing
- References: <20070808060340.4904.bharata@linux.vnet.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- 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.