Re: ARM, registers, "frame 0", where's the PC?

[Daniel Jacobowitz <drow@mvista.com>]

On Wed, Jan 08, 2003 at 08:02:37PM +0100, Torsten Mohr wrote:
> Hi,
> 
> i found out by testing that the first time i stop the target
> and read out its registers, the value of R15 is used in the
> message "Program stopped at 0x12345678".
> 
> When i type in GDB:
> (gdb) info frame
> Stack level 0, frame at 0x1000:
>  pc = 0x12345678; saved pc 0x20203a8
>  (FRAMELESS), called by frame at 0x1000
>  Arglist at 0x1000, args: 
>  Locals at 0x1000, Previous frame's sp in sp
> 
> Could these problems be related to the structures on the
> stack?  When i set R15 to 0x0000 the first time i
> read out the registers, i get the message "Program stopped
> at 0x00000000".  What can i do to tell GDB to use the
> real value in R15?
> 
> I appended a log file of a session, all requests and answers
> are in there.  Is any of the answers not correct?
> 
> Could this be related to the startup code of the test program?
> I attached it to this mail.

Could you show me the log via 'set debug remote 1' instead?

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer