This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: View registers from stack frames

From: Andrew Cagney <cagney at gnu dot org>
To: Fabian Cenedese <Cenedese at indel dot ch>
Cc: gdb at sources dot redhat dot com
Date: Tue, 05 Oct 2004 21:46:26 -0400
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>

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

Follow-Ups:
- Re: View registers from stack frames
  - From: Fabian Cenedese

References:
- Re: View registers from stack frames
  - From: Daniel Jacobowitz
- Re: View registers from stack frames
  - From: Fabian Cenedese
- View registers from stack frames
  - From: Fabian Cenedese
- Re: View registers from stack frames
  - From: Fabian Cenedese

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]