From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6551 invoked by alias); 2 Oct 2007 15:19:42 -0000 Received: (qmail 6506 invoked by uid 48); 2 Oct 2007 15:19:28 -0000 Date: Tue, 02 Oct 2007 15:19:00 -0000 Message-ID: <20071002151928.6505.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 runtime/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/msg00005.txt.bz2 ------- Additional Comments From mhiramat at redhat dot com 2007-10-02 15:19 ------- (In reply to comment #0) > backtrace from timer.profile: > > 0x001d3392 > > -------- > > the profile stack is 0x001d3392 > > -------- > > 0x001d3392 > It was reproduced on my machine with 2.6.22.9-91.fc7. timer.profile will be invoked when a user program is running, and backtracing fails on user stack. I think we need to introduce a function to check whether the probe is in the kernel or in user mode. -- 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.