From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2365 invoked by alias); 3 Oct 2007 19:54:18 -0000 Received: (qmail 2315 invoked by uid 48); 3 Oct 2007 19:54:06 -0000 Date: Wed, 03 Oct 2007 19:54:00 -0000 Message-ID: <20071003195406.2314.qmail@sourceware.org> From: "mhiramat at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20071002142236.5085.wcohen@redhat.com> References: <20071002142236.5085.wcohen@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug testsuite/5085] print_backtrace() and backtrace() not working in timer.profile probe on 2.6.23-rc8 kernel 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: 2007-q4/txt/msg00052.txt.bz2 ------- 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 > > * 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.