From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1838 invoked by alias); 24 Jun 2005 14:10:36 -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 1700 invoked by uid 22791); 24 Jun 2005 14:10:33 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Fri, 24 Jun 2005 14:10:33 +0000 Received: from drow by nevyn.them.org with local (Exim 4.51) id 1Dlot4-0004Ud-T0; Fri, 24 Jun 2005 10:10:30 -0400 Date: Fri, 24 Jun 2005 14:10:00 -0000 From: Daniel Jacobowitz To: maxim@mox.ru Cc: gdb@sources.redhat.com Subject: Re: mips64 gdb problem Message-ID: <20050624141030.GB16942@nevyn.them.org> Mail-Followup-To: maxim@mox.ru, gdb@sources.redhat.com References: <6097c490506240642317a9836@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6097c490506240642317a9836@mail.gmail.com> User-Agent: Mutt/1.5.8i X-SW-Source: 2005-06/txt/msg00231.txt.bz2 On Fri, Jun 24, 2005 at 05:42:25PM +0400, Maxim Osipov wrote: > Hello, > > I have a problem trying to debug 64-bit mips binary with gdb-6.3. It > fails with the following message: > > /home # gdb 64test > GNU gdb 6.3 > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "mips64-linux-gnu"... > ../../gdb-6.3/gdb/dwarf2-frame.c:1411: internal-error: > decode_frame_entry_1: Assertion `fde->cie != NULL' failed. > A problem internal to GDB has been detected, > further debugging may prove unreliable. > Quit this debugging session? (y or n) GCC generates a wacky 64-bit format, otherwise only used on IRIX. I think this is a bug in GCC. GDB could be adapted to generally sort of cope with it, but not completely - there's some ambiguity. -- Daniel Jacobowitz CodeSourcery, LLC