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 04:08:00 -0000 [thread overview]
Message-ID: <20050506040840.GB7038@nevyn.them.org> (raw)
In-Reply-To: <7f45d9390505052049550222ec@mail.gmail.com>
On Thu, May 05, 2005 at 08:49:00PM -0700, Shaun Jackman wrote:
> On 5/5/05, Daniel Jacobowitz <drow@false.org> wrote:
> > On Thu, May 05, 2005 at 08:26:59PM -0700, Shaun Jackman wrote:
> > > arm-elf-gdb 6.2.1 crashed after issuing a 'step' command. Here's the
> > > commands leading up to it and the backtrace.
> >
> > This bug report is still not especially useful, without a reproducible
> > test case. All I can do is recommend you try a current version.
> > There have been plenty of bug fixes since 6.2.1.
>
> I've been having trouble with recent versions of gdb. 6.3 fails while loading:
>
> (gdb) load
> Loading section .text, size 0x64a8 lma 0x2000000
> Memory access error while loading section .text.
Fixed after 6.3, yes.
> 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.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-06 4:08 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 [this message]
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
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=20050506040840.GB7038@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).