From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9757 invoked by alias); 12 Feb 2008 13:31:03 -0000 Received: (qmail 9749 invoked by uid 22791); 12 Feb 2008 13:31:02 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 12 Feb 2008 13:30:42 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 1580398118; Tue, 12 Feb 2008 13:30:41 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id DCD0D9801D; Tue, 12 Feb 2008 13:30:40 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JOvDc-0001Nl-05; Tue, 12 Feb 2008 08:30:40 -0500 Date: Tue, 12 Feb 2008 13:31:00 -0000 From: Daniel Jacobowitz To: Stefan Bylund Cc: gdb@sourceware.org Subject: Re: Does GDB 6.7.1 for PowerPC require the framepointer register for backtracing? Message-ID: <20080212133039.GA5173@caradoc.them.org> Mail-Followup-To: Stefan Bylund , gdb@sourceware.org References: <47B02B7D.40204@enea.se> <20080211130757.GB7796@caradoc.them.org> <47B085BF.7090909@enea.se> <20080211173303.GA19507@caradoc.them.org> <47B173B3.3090801@enea.se> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47B173B3.3090801@enea.se> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-02/txt/msg00066.txt.bz2 On Tue, Feb 12, 2008 at 11:23:47AM +0100, Stefan Bylund wrote: > Hi Daniel, > > Thanks for all your valuable answers! We will use -fomit-frame-pointer as > a workaround for now. Later on we will add support for handling the frame > pointer register in our OS kernel. That seems to be the future-proof > solution. Oh, I see what you mean now. You really have only access to those two registers. Sorry for being dense. I recommend you allow GDB to access the full register set. Future versions of GDB may use any register at all in the unwind information. -- Daniel Jacobowitz CodeSourcery