I compiled kile-1.7_beta2 with empty CFLAGS (using gcc 3.3.4) and USE flag "debug" and FEATURES "nostrip" enabled. Running and using kile causes no trouble. The only problem (I noticed until now) is that when trying to configure kile (settings -> configure kile) kile simply crashes. Then the KDE-crashmanager appears, but it seems impossible to follow the error-stack. Sometimes the crashmanager also does not appear. io ~ # qpkg -i -I -v kile app-editors/kile-1.7_beta2 * A Latex Editor and TeX shell for kde [ http://kile.sourceforge.net ] Compiled with USE Flags: kde debug arts -xinerama Reproducible: Always Steps to Reproduce: 1. launch kile 2. menu: settings -> configure kile 3. Actual Results: kile crashes with the following output in the console: kile: ==KileTool::toolList()================== kile: ==KileTool::Manager::retrieveEntryMap============= kile: BibTeX => Tool/BibTeX/Default kile: ==KileTool::Manager::retrieveEntryMap============= kile: BibTeX => Tool/BibTeX/Default kile: showing pages 2 1 QWidget::setMaximumSize: (m_stackExtra/QWidgetStack) Negative sizes (32767,-1) are not possible KCrash: Application 'kile' crashing... Expected Results: the kile configuration dialog show just show up. Portage 2.0.51_rc7 (gcc34-x86-2004.2, gcc-3.3.4, glibc-2.3.4.20040808-r0, 2.6.8-gentoo-r4 i686) ================================================================= System uname: 2.6.8-gentoo-r4 i686 Intel(R) Pentium(R) M processor 1500MHz Gentoo Base System version 1.5.3 distcc 2.17 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [disabled] Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/share/config:/usr/kde/3.3/env:/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /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/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs distlocks nostrip sandbox" GENTOO_MIRRORS="ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http://ftp.uni-erlangen.de/pub/mirrors/gentoo http://ftp.easynet.nl/mirror/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi alsa anthy apm arts avi berkdb bitmap-fonts bonobo canna cdr cjk crypt cups directfb dvd dvdr encode esd fbcon flac foomaticdb freewnn gdbm ggi gif gimpprint gnome gphoto2 gpm gtk gtk2 gtkhtml guile imlib ipv6 java jpeg kde ldap libg++ libwww lzw-tiff mad mikmod mmx motif mozcalendar mozilla moznocompose moznoirc mozsvg mpeg ncurses nls nptl oggvorbis opengl oss pam pda pdflib perl png ppds python qt quicktime readline ruby samba scanner sdl skk slang spell sse sse2 ssl svg svga tcltk tcpd tetex tiff truetype unicode usb wifi x86 xml xml2 xmms xprint xv xvid zlib linguas_de linguas_ja"
Created attachment 40915 [details] strace output This is the strace output of "strace kile 2> kile.strace.log" "wc -l kile.strace.log" gives 21910
The problem has also been reported at: http://bugs.kde.org/show_bug.cgi?id=89767 The problem seesm to be Gentoo specific.
Well, I just did an update of my gentoo distribution (emerge -up world). It updated a bunch of stuff that seemed unrelated, but it fixed the problem. kile 1.7b2 now works OK.
yes, updating packages helps. now kile 1.7_beta2 works here, too. i updated packages selectively, and i also updated aspell from 0.51 to 6.0.0, so i think maybe it's aspell that caused the crash? or at least, maybe updating to aspell 6.0.0 cures the problem.
I couldn't reproduce this problem. Seems to be a local issue.