I attached gdb to amarokapp when it froze, and tried to get a backtrace. gdb encountered an internal error: (gdb) bt #0 0xb7f19410 in __kernel_vsyscall () #1 0xb604e2be in __lll_mutex_lock_wait () from /lib/libpthread.so.0 #2 0xb6049f51 in _L_mutex_lock_415 () from /lib/libpthread.so.0 dwarf2-frame.c:490: internal-error: Unknown CFI encountered. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y dwarf2-frame.c:490: internal-error: Unknown CFI encountered. A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) y Aborted (core dumped) This was gdb 6.4. emerge --info: Portage 2.1.1-r1 (default-linux/x86/2006.0, gcc-4.1.1, glibc-2.5-r0, 2.6.18-gentoo i686) ================================================================= System uname: 2.6.18-gentoo i686 AMD Athlon(tm) XP 2000+ Gentoo Base System version 1.12.5 Last Sync: Mon, 30 Oct 2006 21:00:01 +0000 app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r4 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r1 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-march=athlon-xp -O2 -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/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/" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo" CXXFLAGS="-march=athlon-xp -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" GENTOO_MIRRORS="ftp://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://gentoo.noved.org/" LC_ALL="en_US.UTF-8" LINGUAS="en uk ru" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 3dnow X aac aalib acl acpi aim alsa apache2 asf audiofile bcmath bitmap-fonts browserplugin bzip2 cairo cdparanoia cli cracklib crypt css cups curl dbus dga directfb divx4linux dlloader dri dvd dvdr elibc_glibc emboss encode fam fbcon fbsplash ffmpeg flash foomaticdb gdbm gif glitz glut gpm gstreamer gtk gtk2 hal iconv icq idn imlib input_devices_keyboard input_devices_mouse ipv6 isdnlog javascript jikes jpeg jpeg2k kde kdeenablefinal kdehiddenvisibility kernel_linux lcms lesstif libg++ libwww linguas_en linguas_ru linguas_uk live lm_sensors logitech-mouse mad mikmod mmx mng mp3 mpeg mplayer msn mtp musicbrainz ncurses nls nptl nptlonly nsplugin offensive ogg openexr opengl oscar pam pcre pdf pic png povray ppds pppd qt3 qt4 quicktime rdesktop readline reflection rtc samba scanner sdl session sftplogging slp snmp speex spell spl sse ssl startup-notification subversion svg sysfs tcpd tetex theora tiff timidity truetype truetype-fonts type1-fonts udev unicode usb userland_GNU video_cards_ati video_cards_radeon vorbis wifi win32codecs xcomposite xine xinerama xml xorg xscreensaver xv xvid yahoo zeroconf zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Created attachment 100915 [details] Complete log
Is there a way to get a backtrace of gdb's crash? I compiled gdb with USE=debug, FEATURES=nostrip, CFLAGS=-g, but the only backtrace I am getting is: (gdb) bt #0 0xb7fd2410 in ?? () #1 0xbfb172d8 in ?? () #2 0x00000006 in ?? () #3 0x0000212c in ?? () #4 0xb7e2e19e in raise () from /lib/libc.so.6 #5 0xb7f46ff4 in ?? () from /lib/libc.so.6 #6 0xb7e028d0 in ?? () #7 0xb7e2fb5c in abort () from /lib/libc.so.6 #8 0xbfb17210 in ?? () #9 0x00000000 in ?? ()
try with the latest gdb-6.5 ebuild
Ok, I upgraded to 6.5... That bug is still present, but now there's also a new one. It's an actual segmentation fault, not an internal error: Program terminated with signal 11, Segmentation fault. #0 0x08096101 in _initialize_thread_db () (gdb) bt #0 0x08096101 in _initialize_thread_db () #1 0x0809650a in _initialize_thread_db () #2 0x08110b46 in normal_stop () #3 0x08084da0 in discard_cleanups () #4 0x0811bd8a in throw_exception () #5 0x0811be50 in throw_exception () #6 0x0811beac in throw_verror () #7 0x08087c93 in error () #8 0x08087f69 in perror_with_name () #9 0x08094eb5 in supply_gregset () #10 0x0809bb07 in linux_record_stopped_pid () #11 0x08097d6b in _initialize_thread_db () #12 0x0811195f in resume () #13 0x08111b5b in resume () #14 0x08112cc0 in handle_inferior_event () #15 0x0811415c in wait_for_inferior () #16 0x081142e5 in proceed () #17 0x0810f039 in continue_command () #18 0x08084032 in execute_command () #19 0x0811fb68 in push_prompt () #20 0x08120898 in display_gdb_prompt () #21 0x081cb144 in rl_callback_read_char () #22 0x0811fd1b in push_prompt () #23 0x0811f680 in gdb_do_one_event () #24 0x0811eb1b in delete_async_signal_handler () #25 0x0811f2a2 in gdb_do_one_event () #26 0x0811c0b3 in catch_errors () #27 0x080c56a4 in _initialize_tui_interp () #28 0x0811c6ff in current_interp_command_loop () #29 0x0807d33b in gdb_main () #30 0x0811c0b3 in catch_errors () #31 0x0807db0b in gdb_main () #32 0x0811c0b3 in catch_errors () #33 0x0807d321 in gdb_main () #34 0x0807d2e5 in main ()
How about now? We are all the way up to 6.7.1 :)
