From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5272 invoked by alias); 6 Oct 2004 01:46:59 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 5265 invoked from network); 6 Oct 2004 01:46:58 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 6 Oct 2004 01:46:58 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i961krbR014641 for ; Tue, 5 Oct 2004 21:46:53 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i961kfr03597; Tue, 5 Oct 2004 21:46:42 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D606728D2; Tue, 5 Oct 2004 21:46:26 -0400 (EDT) Message-ID: <41634E72.70205@gnu.org> Date: Wed, 06 Oct 2004 01:57:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040831 MIME-Version: 1.0 To: Fabian Cenedese Cc: gdb@sources.redhat.com Subject: Re: View registers from stack frames References: <20041005140227.GA13586@nevyn.them.org> <5.2.0.9.1.20041005154532.01d52ec0@NT_SERVER> <5.2.0.9.1.20041005142840.01d03818@NT_SERVER> <5.2.0.9.1.20041005142840.01d03818@NT_SERVER> <5.2.0.9.1.20041005154532.01d52ec0@NT_SERVER> <5.2.0.9.1.20041005171658.01d208e0@NT_SERVER> In-Reply-To: <5.2.0.9.1.20041005171658.01d208e0@NT_SERVER> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00105.txt.bz2 > It is better in so far as the pc did change from frame 0 to frame 1. > But now reading the whole call stack is messed up. Funny though > that only the pc stays the same, other values do change. That's a separate bug - the new frame unwind code is running into trouble. I'd check a current gdb (:-/), and if no luck, post more details here - KevinB is the PPC maintainer. > That was with exactly the same setup as before. But maybe gdb-6.2 > needs different values from the stub...? If I go back to gdb-6.1.1 > it works again. > > Should I try an even newer gdb then? Andrew