From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4835 invoked by alias); 6 May 2005 03:49:07 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 4686 invoked from network); 6 May 2005 03:49:00 -0000 Received: from unknown (HELO rproxy.gmail.com) (64.233.170.192) by sourceware.org with SMTP; 6 May 2005 03:49:00 -0000 Received: by rproxy.gmail.com with SMTP id z35so672246rne for ; Thu, 05 May 2005 20:49:00 -0700 (PDT) Received: by 10.11.94.35 with SMTP id r35mr20975cwb; Thu, 05 May 2005 20:49:00 -0700 (PDT) Received: by 10.11.99.70 with HTTP; Thu, 5 May 2005 20:49:00 -0700 (PDT) Message-ID: <7f45d9390505052049550222ec@mail.gmail.com> Date: Fri, 06 May 2005 03:49:00 -0000 From: Shaun Jackman Reply-To: Shaun Jackman To: gdb@sources.redhat.com Subject: Re: arm-elf-gdb crash In-Reply-To: <20050506033126.GA6920@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <7f45d9390505052026171614fd@mail.gmail.com> <20050506033126.GA6920@nevyn.them.org> X-SW-Source: 2005-05/txt/msg00068.txt.bz2 On 5/5/05, Daniel Jacobowitz 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. >=20 > 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 loadi= ng: (gdb) load Loading section .text, size 0x64a8 lma 0x2000000 Memory access error while loading section .text. 6.3.50.20050419 fixes the load bug, but fails when setting the $cpsr (gdb) set $cpsr=3D0x1f Value being assigned to is no longer active. Do you know if the $cpsr bug has been fixed in a recent snapshot? Cheers, Shaun