linux-mips
[Top] [All Lists]

Fwd: mips64 gdb problem

To: linux-mips@linux-mips.org
Subject: Fwd: mips64 gdb problem
From: Maxim Osipov <maxim.osipov@gmail.com>
Date: Fri, 24 Jun 2005 19:41:48 +0400
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=iWU2KgEztMWE3O5zi89zJ7GW74ThQhn7JVdX+PbQi7yJQxA0+tZXGT48h9qTjY/Gc20oHABOI9tQnVezTUyN85ZQxhJ1yFQbPu1rg5YBfoueSsuIHc+TmjUqzZH1A1eY5JGH5O7wGudlHSX8qN4WbNE7O7OuShc9p5hM5ysm4QI=
In-reply-to: <20050624141030.GB16942@nevyn.them.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <6097c490506240642317a9836@mail.gmail.com> <20050624141030.GB16942@nevyn.them.org>
Reply-to: maxim@mox.ru
Sender: linux-mips-bounce@linux-mips.org
Hello,

I wonder, is there some way to get debuger working on N64 target?

Thanks,
Maxim

---------- Forwarded message ----------
From: Daniel Jacobowitz <drow@false.org>
Date: Jun 24, 2005 6:10 PM
Subject: Re: mips64 gdb problem
To: maxim@mox.ru
Cc: gdb@sources.redhat.com


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

<Prev in Thread] Current Thread [Next in Thread>
  • Fwd: mips64 gdb problem, Maxim Osipov <=