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

[Torsten Mohr <tmohr@s.netic.de>]

Hi,

i received a hint by mail to send ALL registers from the
GDB remote protocol server back to arm-unknown-elf-insight.

I now do that but it i still get this unwanted behaviour:

I can download a program, start it, stop it, read registers
(the correct values are shown, as i see in the debug output
of my debug server).  The values make sense, R15 is exactly
where i expect it to be.

But when i stop the program, "insight" tells me that it
stopped at 0x01002048.  That's nowhere in my program
and not what's shown in R15.

In the GDB console, "info registers" shows the same values
as in "insight".  Especially "p/x $pc" says 0x02020070
what makes sense and is correct.

In "info gdb" i read:

   Normally, register values are relative to the selected stack frame
(*note Selecting a frame: Selection.).  This means that you get the
value that the register would contain if all stack frames farther in
were exited and their saved registers restored.  In order to see the
true contents of hardware registers, you must select the innermost
frame (with `frame 0').

When i type "frame 0", gdb says:
gdb) frame 0
#0  0x01002048 in ?? ()

This seems to be related to the problem.  I have to admit i don't
understand that.  Why can't GDB say where it stopped, it has the
correct value for R15.  Also, inbetween the stop ("\x03") and the
reading of the registers ("g") there is no other request from
GDB.  What info is missing?


Thanks for any hints,
Torsten.