From: Daniel Jacobowitz <drow@false.org>
To: Shaun Jackman <sjackman@gmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: arm-elf-gdb crash
Date: Fri, 06 May 2005 15:42:00 -0000 [thread overview]
Message-ID: <20050506154214.GA5359@nevyn.them.org> (raw)
In-Reply-To: <7f45d93905050608406479775b@mail.gmail.com>
On Fri, May 06, 2005 at 08:40:00AM -0700, Shaun Jackman wrote:
> On 5/5/05, Daniel Jacobowitz <drow@false.org> wrote:
> > > 6.3.50.20050419 fixes the load bug, but fails when setting the $cpsr
> > > (gdb) set $cpsr=0x1f
> > > Value being assigned to is no longer active.
> > >
> > > Do you know if the $cpsr bug has been fixed in a recent snapshot?
> >
> > I discussed this with someone else on this list last week. It is an
> > open bug but someone needs to sit down with it and think about the
> > implications.
>
> The implications meaning the possible causes, or the implications of
> possible solutions?
The latter.
> > I suspect that we've failed to create the first frame, somehow.
>
> Perhaps this would only defer the problem, but in the case of
> assigning to a register that's never going away, could we skip the
> check for a valid frame and plow ahead and write the register?
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.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-06 15:42 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 [this message]
2005-05-06 16:03 ` Shaun Jackman
2005-09-20 16:35 ` Shaun Jackman
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=20050506154214.GA5359@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=sjackman@gmail.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).