public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Shaun Jackman <sjackman@gmail.com>
To: gdb@sources.redhat.com
Subject: Re: arm-elf-gdb crash
Date: Tue, 20 Sep 2005 16:35:00 -0000	[thread overview]
Message-ID: <7f45d939050920093549bc0d9e@mail.gmail.com> (raw)
In-Reply-To: <7f45d93905050609033ff95af9@mail.gmail.com>

2005/5/6, Shaun Jackman <sjackman@gmail.com>:
> On 5/6/05, Daniel Jacobowitz <drow@false.org> wrote:
> > GDB associates registers to frames.  It's written to the assumption
> > that there is always a frame; when there isn't, this is just one of
> > many things that is going to go wrong.
> 
> When the target's gone toes-up like this, normally I don't want to do
> any further source-level debugging. I'm more interested in peeking and
> poking a few registers to do some post-mortem analysis before I reload
> the target. When a frame isn't available, could GDB fall back to a set
> of global registers?
> 
> Cheers,
> Shaun

Hello,

This is a quick poll to see if there's been any movement on the "Value
being assigned to is no longer active." bug. It haunts me daily.

(gdb) set $cpsr=0x1f
Value being assigned to is no longer active.

Cheers!
Shaun

      reply	other threads:[~2005-09-20 16:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06  3:27 Shaun Jackman
2005-05-06  3:31 ` Daniel Jacobowitz
2005-05-06  3:49   ` Shaun Jackman
2005-05-06  4:08     ` Daniel Jacobowitz
2005-05-06 15:40       ` Shaun Jackman
2005-05-06 15:42         ` Daniel Jacobowitz
2005-05-06 16:03           ` Shaun Jackman
2005-09-20 16:35             ` Shaun Jackman [this message]

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=7f45d939050920093549bc0d9e@mail.gmail.com \
    --to=sjackman@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).