This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel
- From: "mhiramat at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 3 Oct 2007 19:54:06 -0000
- Subject: [Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel
- References: <20071002142236.5085.wcohen@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From mhiramat at redhat dot com 2007-10-03 19:54 -------
(In reply to comment #5)
> I thought I fixed this last week. Do you have this in testsuite/ChangeLog?
> 2007-09-25 Martin Hunt <hunt@redhat.com>
>
> * systemtap.context/backtrace.tcl: Handle single line timer.profile
> backtraces.
Thanks to fix that, however, I think that is not related to this issue.
(In my case, I used the latest cvs source code.)
it is hard to get the function name from userspace without debuginfo of the
application. So, I recommend to skip the timer.profile handler in the test if it
is invoked in userspace. I think we can check that by using probefunc().
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5085
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.