This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/5667] Exploit kprobe.symbol_name for function boundary tracing
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 28 Jan 2008 05:37:11 -0000
- Subject: [Bug translator/5667] Exploit kprobe.symbol_name for function boundary tracing
- References: <20080125095214.5667.ananth@in.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2008-01-28 05:37 -------
(In reply to comment #3)
> Out intention is, If user doesn't have the debuginfo package and he wants do
> function boundry tracing then kprobe-specific symbol-name approach helps.
(Yes, but elfutils usage does not imply dwarf debuginfo dependence.)
> In that direction, We need to read just function name from the script and
> assign it to kp.symbol_name.
Drawbacks include that then you cannot do any verification until run time,
nor can you have wildcards. Maybe you can use a RH-style System.map file
at translate time instead.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5667
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.