Bug 88220 – gdb fails with dwarf2-frame.c:1411: internal-error:

• Product: Gentoo Linux
• Status: RESOLVED UPSTREAM

[Description Dmitri Pogosian 2005-04-06 17:25:57 UTC]

I have f90 executable, compiled with intel ifort for EM64T compiler.

Launching gdb (I have tried both gdb-6.0-r1 and ~amd64 gdb-6.3 with the same
results) gives

bash-2.05b$ gdb topmarg
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 "x86_64-pc-linux-gnu"...
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)

[Comment 1 SpanKY 2005-04-06 17:49:22 UTC]

you neglected to provide `emerge info` like the bug report page told you to ...

could you post the binary you're trying to debug and/or some source code ?

[Comment 2 Dmitri Pogosian 2005-04-06 19:04:04 UTC]

Actually, I got into New-Expert mode (following the link from another bug) and nowhere along the process the bug system told me to submit 'emerge info'

> emerge info

Portage 2.0.51.19 (default-linux/amd64/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r3 x86_64)
=================================================================
System uname: 2.6.11-gentoo-r3 x86_64 AMD Opteron(tm) Processor 248
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 12 2005, 22:24:07)]
distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r7
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.6.8.1-r4
ACCEPT_KEYWORDS="amd64"
AUTOCLEAN="yes"
CFLAGS="-O2"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox"
GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="amd64 X acpi alsa arts berkdb bitmap-fonts cdparanoia cdr crypt cups curl dvd dvdr fam font-server foomaticdb fortran gif gpm gtk gtk2 imagemagick imlib java jp2 jpeg kde libwww lzw lzw-tiff motif mp3 ncurses nls nptl opengl oss pam perl png ppds python qt readline sdl server spell ssl tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts unicode usb xinerama xml2 xmms xpm xrandr xv zlib"Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY

My executable is 3Mb and attachement does not work.  
ifort compilation options are

FFLAGS  = -O -w -static-libcxa -g

[Comment 3 SpanKY 2005-04-06 19:09:09 UTC]

if you submit a bug with the 'expert' mode we assume you know what you're doing and you know that you're supposed to post `emerge info`

if you cant compress & attach the executable then what about the source ?

[Comment 4 Dmitri Pogosian 2005-04-06 19:35:24 UTC]

Created attachment 55533 [details]
gzipped executable

[Comment 5 Dmitri Pogosian 2005-04-06 19:36:07 UTC]

Haven't realized compression is effective on executables.
Have attached topmarg.gz

[Comment 6 SpanKY 2005-04-06 19:43:54 UTC]

on second thought, it'd prob be best to try and get this resolved at the GDB bug tracker: http://sources.redhat.com/gdb/bugs/

[Comment 7 SpanKY 2005-04-20 19:27:00 UTC]

please file a bug upstream