Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Decker, Paul" <Paul.Decker@analog.com>
To: <gdb@sources.redhat.com>
Subject: Value being assigned to is no longer active.
Date: Tue, 03 May 2005 12:41:00 -0000	[thread overview]
Message-ID: <E21A9A52FF03B249B20F0DC563DEBB31191D4032@nwd2exm3.ad.analog.com> (raw)

 

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


             reply	other threads:[~2005-05-03 12:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-03 12:41 Decker, Paul [this message]
2005-05-03 12:58 ` Daniel Jacobowitz
  -- strict thread matches above, loose matches on Subject: below --
2005-05-03 14:01 Decker, Paul
2005-05-03 13:47 Decker, Paul
2005-05-03 13:54 ` Daniel Jacobowitz
2005-05-03 13:38 Decker, Paul
2005-05-03 13:40 ` Daniel Jacobowitz
2005-05-03 13:03 Decker, Paul
2005-05-03 13:21 ` Daniel Jacobowitz
2005-04-20 23:58 Shaun Jackman
2005-04-21  0:47 ` Daniel Jacobowitz
2005-04-21  3:16   ` Shaun Jackman
2005-04-21  3:18     ` Daniel Jacobowitz
2005-04-21  3:41       ` Shaun Jackman
2005-04-27 16:39   ` Shaun Jackman
2005-04-27 18:40     ` Daniel Jacobowitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E21A9A52FF03B249B20F0DC563DEBB31191D4032@nwd2exm3.ad.analog.com \
    --to=paul.decker@analog.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox