This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: latest gdb snapshot issues with ecos binaries
- From: Michael Malone <michael dot malone at tait dot co dot nz>
- To: gdb at sourceware dot org
- Date: Mon, 26 Jan 2009 11:20:19 +1300
- Subject: Re: latest gdb snapshot issues with ecos binaries
I got the same symptom whether I used the ubuntu packaged version or the
snapshot. For the example I got lazy and just used the version on my
$PATH. Though if there's a library somewhere that might make a
difference, let me know and I'll remove the older version. For now,
here's the same out from the snapshot version.
Thanks,
Michael
GNU gdb (GDB) 6.8.50.20090122
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
dwarf2-frame.c:1769: internal-error: decode_frame_entry_1: Assertion
`fde->cie != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Daniel Jacobowitz wrote:
On Fri, Jan 23, 2009 at 06:02:53PM +1300, Michael Malone wrote:
GNU gdb 6.8
This is using yesterday's snapshot (Jan 22) of GDB from CVS. I got the
same thing when I used the version of gdb that came with gcc-4.2.3
Does anyone know what's going wrong or of a workaround?
Are you sure you're using a snapshot? It should have a version like
6.8.50.0.<date>.
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================