Re: Value being assigned to is no longer active.

[Shaun Jackman <sjackman@gmail.com>]

On 4/20/05, Daniel Jacobowitz <drow@false.org> wrote:
> On Wed, Apr 20, 2005 at 04:58:24PM -0700, Shaun Jackman wrote:
> > What does this error message mean?
> >
> > (gdb) set $cpsr=0x1f
> > Value being assigned to is no longer active.
> > (gdb) set $pc=0x2000000
> > Value being assigned to is no longer active.
> > (gdb) show version
> > GNU gdb 6.3.50.20050419
> > ...
> > This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf".
> 
> In this context, I'm not sure.  Could you show a whole session?

Here's a complete session. I loaded and ran the program. It hung so I
interrupted it. I tried a backtrace, but the processor was in
no-man's-land, so I attempted to switch the chip back to user-mode to
see what its stack looked like.

Cheers,
Shaun

(gdb) target remote bdi:2001
Remote debugging using bdi:2001
0x01009810 in ?? ()
(gdb) lo
Loading section .text, size 0x2ece8 lma 0x2000000
Loading section .rodata, size 0x7e30 lma 0x202ece8
Loading section .data, size 0x19c8 lma 0x2036c18
Start address 0x2000000, load size 230624
Transfer rate: 108528 bits/sec, 312 bytes/write.
(gdb) c
Continuing.

Program received signal SIGSTOP, Stopped (signal).
0x00000010 in ?? ()
(gdb) bt
#0  0x00000010 in ?? ()
(gdb) p/x $cpsr
$1 = 0x20000097
(gdb) set $cpsr=0x1f
Value being assigned to is no longer active.
(gdb) p/x $cpsr=0x1f
Value being assigned to is no longer active.