From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19715 invoked by alias); 5 Oct 2004 14:22:57 -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 19665 invoked from network); 5 Oct 2004 14:22:54 -0000 Received: from unknown (HELO smtp.hispeed.ch) (62.2.95.247) by sourceware.org with SMTP; 5 Oct 2004 14:22:54 -0000 Received: from indel.ch (217-162-27-127.dclient.hispeed.ch [217.162.27.127]) by smtp.hispeed.ch (8.12.6/8.12.6/tornado-1.0) with SMTP id i95EMrpd024985 for ; Tue, 5 Oct 2004 16:22:53 +0200 Received: from fabi.indel.ch [192.168.1.19] by indel.ch [127.0.0.1] with SMTP (MDaemon.v2.7.SP5.R) for ; Tue, 05 Oct 2004 16:20:59 +0200 Message-Id: <5.2.0.9.1.20041005162110.01d03818@NT_SERVER> X-Sender: cenedese@NT_SERVER (Unverified) Date: Tue, 05 Oct 2004 15:00:00 -0000 To: gdb@sources.redhat.com From: Fabian Cenedese Subject: Re: View registers from stack frames In-Reply-To: <20041005140227.GA13586@nevyn.them.org> References: <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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-MDaemon-Deliver-To: gdb@sources.redhat.com X-Return-Path: cenedese@indel.ch X-SW-Source: 2004-10/txt/msg00092.txt.bz2 >> >>With the stack commands (frame, up, down) I can select a different >> >>stack frame. Local variables and arguments (even with same name) >> >>have different values, depending on the stack frame number. But it >> >>seems that registers aren't corrected for previous stack frames. Is >> >>this correct? e.g. the PC and LR should change their value on every >> >>frame, and the PC was the last LR. But "info reg" always shows the >> >>same values. Is there any way to get the previous frame's registers? >> >>When I do "info frame x" I get something like "saved pc 0x..." so at >> >>least this information is available, why isn't this put into the register >> >>overview? And what about the other SPRs and GPRs? >> > >> >You've just described the expected and correct behavior. That makes it sound like an architecture specific bug. Which architecture system is this on, and can you post a transcript. >> >> I'm using a self built gdb-6.1.1 for PPC-targets and cygwin. The >> communication with the target is over a stub-server to a PPC-board. > >For PPC, try 6.2 instead. > >As Andrew already explained, this is what is supposed to happen. It >did not used to work but was fixed by the new frame architecture. Ok, I will try 6.2 then. Thanks bye Fabi