All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bryan Althouse" <bryan.althouse@3phoenix.com>
To: "'Maxim Osipov'" <maxim.osipov@gmail.com>
Cc: <linux-mips@linux-mips.org>
Subject: re: Fwd: mips64 gdb problem
Date: Mon, 25 Jul 2005 16:39:56 -0400	[thread overview]
Message-ID: <20050725203743Z8225534-3678+4331@linux-mips.org> (raw)

I'm butting heads with this problem also.  I get the error below when
running mips64-unknown-linux-gdb on a 64 bit mips binary.  Has anyone come
up with a work around?

Thanks,
Bryan

>Hello,
>I wonder, is there some way to get debuger working on N64 target?
>Thanks,
>Maxim

>>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.

WARNING: multiple messages have this Message-ID (diff)
From: "Bryan Althouse" <bryan.althouse@3phoenix.com>
To: 'Maxim Osipov' <maxim.osipov@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: re: Fwd: mips64 gdb problem
Date: Mon, 25 Jul 2005 16:39:56 -0400	[thread overview]
Message-ID: <20050725203743Z8225534-3678+4331@linux-mips.org> (raw)
Message-ID: <20050725203956.EXg4dASleqI313DIyzNGd3iJ0bozvlw8RXfUkU_T5Ig@z> (raw)

I'm butting heads with this problem also.  I get the error below when
running mips64-unknown-linux-gdb on a 64 bit mips binary.  Has anyone come
up with a work around?

Thanks,
Bryan

>Hello,
>I wonder, is there some way to get debuger working on N64 target?
>Thanks,
>Maxim

>>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.

             reply	other threads:[~2005-07-25 20:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 20:39 Bryan Althouse [this message]
2005-07-25 20:39 ` Fwd: mips64 gdb problem Bryan Althouse
     [not found] <42e57109.14b0f52a.28ce.3671SMTPIN_ADDED@mx.gmail.com>
2005-07-26  3:23 ` Maxim Osipov
     [not found] <6097c490506240642317a9836@mail.gmail.com>
     [not found] ` <20050624141030.GB16942@nevyn.them.org>
2005-06-24 15:41   ` 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=20050725203743Z8225534-3678+4331@linux-mips.org \
    --to=bryan.althouse@3phoenix.com \
    --cc=linux-mips@linux-mips.org \
    --cc=maxim.osipov@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.