Value being assigned to is no longer active.

["Decker, Paul" <Paul dot Decker at analog dot com>]

Being relatively new to using gdb, and developing a new target for it,
I'm now getting this same error message.  I get it, after I have loaded
a program to my target.  Before performing a load, I can set register
values without any problems.  The load seems to work fine, however at
that point, I can not set any register values, including the PC.

I would be grateful for any ideas, remember though, I'm very green with
gdb and the whole debug server stuff.

thanks,
Paul.





-----Original Message-----
From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com]
On Behalf Of Daniel Jacobowitz
Sent: Wednesday, April 20, 2005 11:18 PM
To: Shaun Jackman
Cc: gdb@sources.redhat.com
Subject: Re: Value being assigned to is no longer active.

On Wed, Apr 20, 2005 at 08:16:37PM -0700, Shaun Jackman wrote:
> 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?
> 
> In the following snippet, the target hung after the "s", so I pressed
Ctrl-c.
> 
> Cheers,
> Shaun
> 
> (gdb) s
> Program received signal SIGSTOP, Stopped (signal).
> 0x0000000c in ?? ()
> (gdb) bt
> #0  0x0000000c in ?? ()
> (gdb) p/x $cpsr
> $1 = 0x40000093
> (gdb) set $cpsr=0x1f
> Value being assigned to is no longer active.

We'd need to be able to reproduce the problem.

I suspect that we've failed to create the first frame, somehow.

--
Daniel Jacobowitz
CodeSourcery, LLC