From: Maxim Osipov <maxim.osipov@gmail.com>
To: linux-mips@linux-mips.org
Subject: Fwd: mips64 gdb problem
Date: Fri, 24 Jun 2005 19:41:48 +0400 [thread overview]
Message-ID: <6097c4905062408414be88eb5@mail.gmail.com> (raw)
In-Reply-To: <20050624141030.GB16942@nevyn.them.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
next parent reply other threads:[~2005-06-24 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6097c490506240642317a9836@mail.gmail.com>
[not found] ` <20050624141030.GB16942@nevyn.them.org>
2005-06-24 15:41 ` Maxim Osipov [this message]
2005-07-25 20:39 Fwd: mips64 gdb problem Bryan Althouse
2005-07-25 20:39 ` Bryan Althouse
[not found] <42e57109.14b0f52a.28ce.3671SMTPIN_ADDED@mx.gmail.com>
2005-07-26 3:23 ` Maxim Osipov
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=6097c4905062408414be88eb5@mail.gmail.com \
--to=maxim.osipov@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=maxim@mox.ru \
/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