From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22068 invoked by alias); 13 Oct 2006 14:38:54 -0000 Received: (qmail 22060 invoked by uid 22791); 13 Oct 2006 14:38:53 -0000 X-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 13 Oct 2006 14:38:47 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k9DEcjxa029927; Fri, 13 Oct 2006 10:38:45 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.12.11.20060308/8.12.11) with ESMTP id k9DEcjCN001061; Fri, 13 Oct 2006 10:38:45 -0400 Received: from vpn-248-77.boston.redhat.com (vpn-248-77.boston.redhat.com [10.13.248.77]) by pobox.corp.redhat.com (8.13.1/8.12.8) with ESMTP id k9DEciHr013798; Fri, 13 Oct 2006 10:38:44 -0400 Subject: Re: stack trace changes From: Martin Hunt To: Mike Mason Cc: systemtap@sources.redhat.com In-Reply-To: <452EBF4A.8000500@us.ibm.com> References: <1160679497.4762.11.camel@dragon> <452EBF4A.8000500@us.ibm.com> Content-Type: text/plain Organization: Red Hat Inc. Date: Fri, 13 Oct 2006 14:38:00 -0000 Message-Id: <1160750323.2535.9.camel@dragon> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q4/txt/msg00109.txt.bz2 On Thu, 2006-10-12 at 15:18 -0700, Mike Mason wrote: > I tested print_backtrace on 2.6.17-1.2187_FC5 on x86_64. I now see a > single line(as before) followed by "Inexact backtrace:" and then > nothing. Are you using the example from 3050? probe kernel.function("schedule@kernel/sched.c") { print_backtrace(); } On RHEL4 (2.6.9-42.0.3.ELsmp), I get 0xffffffff80309677 : schedule+0x15/0xb6f [] Inexact backtrace: 0xffffffff8010e7f4 : cpu_idle+0x32/0x34 [] 0xffffffff804eb67b : start_kernel+0x1d6/0x1da [] 0xffffffff804eb1d5 : _sinittext+0x1d5/0x1d7 [] 0xffffffff80309677 : schedule+0x15/0xb6f [] Inexact backtrace: 0xffffffff8013575f : autoremove_wake_function+0x9/0x2e [] 0xffffffff80133dfe : __wake_up_common+0x43/0x63 [] 0xffffffff80147795 : worker_thread+0xe2/0x22a [] 0xffffffff80133dad : default_wake_function+0x0/0xe [] 0xffffffff80133dad : default_wake_function+0x0/0xe [] 0xffffffff8014b4f4 : keventd_create_kthread+0x0/0x48 [] 0xffffffff801476b3 : worker_thread+0x0/0x22a [] 0xffffffff8014b4f4 : keventd_create_kthread+0x0/0x48 [] 0xffffffff8014b4cb : kthread+0xc8/0xf1 [] 0xffffffff80110f47 : child_rip+0x8/0x11 [] 0xffffffff8014b4f4 : keventd_create_kthread+0x0/0x48 [] 0xffffffff8014b403 : kthread+0x0/0xf1 [] 0xffffffff80110f3f : child_rip+0x0/0x11 [] 0xffffffff80309677 : schedule+0x15/0xb6f [] Inexact backtrace: 0xffffffff8010e7f4 : cpu_idle+0x32/0x34 [] [...] I don't have FC5 installed on x86_64, but I tried FC6 with the new unwinder disabled and it worked just like it did with the old 2.6.9 kernel. So it should work.