Bug 132731 – gaim 1.5 (and 2beta) crashes with gtk+-2.8.17

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Federico Fissore 2006-05-08 14:42:50 UTC]

after gnome2.14 upgrade, even gtk was upgraded from 2.8.13 to 2.8.17
before the upgrade gaim was working perfectly. now gaim is crashing after some chars typed in a message window, or just after a click on "info" on a contact

i suspect this is due to some gtk upgrade as, i think, this backtrace says

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208908112 (LWP 28460)]
Error while running hook_stop:
Invalid type combination in ordering comparison.
0x468d21d4 in gtk_text_insert () from /usr/lib/libgtk-x11-2.0.so.0
gdb> bt full
#0  0x468d21d4 in gtk_text_insert () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#1  0xbfc36488 in ?? ()
No symbol table info available.
#2  0xbfc36490 in ?? ()
No symbol table info available.
#3  0xbfc36470 in ?? ()
No symbol table info available.
#4  0x46a29e18 in gtk_interface_age () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#5  0x469a2fa2 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#6  0x46a29e18 in gtk_interface_age () from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#7  0x00000142 in ?? ()
No symbol table info available.
#8  0x08345650 in ?? ()
No symbol table info available.
#9  0x0834f8a0 in ?? ()
No symbol table info available.
#10 0x0000002f in ?? ()
No symbol table info available.
#11 0x0000002f in ?? ()
No symbol table info available.
#12 0x00000142 in ?? ()
No symbol table info available.
#13 0xffffffff in ?? ()
No symbol table info available.
#14 0x60cd94d3 in ?? ()
No symbol table info available.
#15 0x924eb4cf in ?? ()
No symbol table info available.
#16 0x0834f930 in ?? ()
No symbol table info available.
#17 0x0834f690 in ?? ()
No symbol table info available.
#18 0x00000000 in ?? ()
No symbol table info available.
gdb>

sorry for the missing debug simbols. i have debug disabled. if you are not able to reproduce the bug, i will re-emerge gtk+ with debug

Portage 2.1_pre10-r4 (default-linux/x86/2005.1, gcc-4.1.0, glibc-2.4-r2, 2.6.14-gentoo-r5 i686)
=================================================================
System uname: 2.6.14-gentoo-r5 i686 AMD Athlon(tm) XP 1700+
Gentoo Base System version 1.12.0_pre19
ccache version 2.4 [enabled]
dev-lang/python:     2.3.5-r2, 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache:     2.4-r1
dev-util/confcache:  [Not Present]
sys-apps/sandbox:    1.2.18
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-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r5
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer -ftracer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/share/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=athlon-xp -pipe -fomit-frame-pointer -ftracer -fvisibility-inlines-hidden"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="-D --nospinner"
FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict"
GENTOO_MIRRORS="http://mirror.switch.ch/ftp/mirror/gentoo/"
LDFLAGS="-Wl,-O1"
MAKEOPTS="-j2 -s"
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"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 3dnow X a52 aac aalib acpi alsa apm asf avahi avi berkdb bitmap-fonts bzip2 cairo cdda cdr cli crypt css cups dbus dga dri dts dvb dvd dvdr dvdread eds emboss encode esd ffmpeg firefox foomaticdb fortran gcj gdbm gif glitz glut gnome gpm gstreamer gtk gtk2 imlib ipv6 isdnlog java jikes jpeg libcaca libg++ libwww live lzo mad matroska mikmod mjpeg mmx mmxext mng motif mp3 mp4 mpeg nautilus ncurses nls nptl nptlonly nsplugin nvidia ogg oggvorbis openal opengl pam pcre pdflib perl png pppd python quicktime readline real reflection rtc ruby samba sdl session smartcard spell spl sse ssl startup-notification stream svg tcpd theora threads tiff truetype truetype-fonts type1-fonts vcd vlm vorbis win32codecs wmf wxwindows x264 xine xml2 xmms xorg xosd xv xvid xvmc zlib elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux userland_GNU video_cards_nv video_cards_nvidia video_cards_vesa"
Unset:  ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

[Comment 1 Kathryn Kulick (RETIRED) 2006-05-08 14:51:27 UTC]

I suspect you are right about it being gtk related. Please try and rebuild gaim against the new gtk and let me know what happens.

[Comment 2 Federico Fissore 2006-05-08 14:58:14 UTC]

a similar problem occured with gedit when selecting all the text (with ctrl+a).
running gdb against it, the exact message

gtk_text_insert () from /usr/lib/libgtk-x11-2.0.so.0

appeared

i'm downgrading to gtk 2.8.13 to see if this fixes this issues

[Comment 3 Federico Fissore 2006-05-08 15:37:36 UTC]

i re-emerge gtk 2.8.17 with the debug use flag, and now gaim and gedit aren't crashing anymore :(

i'll stay with the debug gtk and keep you updated if the problem occurs again

[Comment 4 Federico Fissore 2006-05-09 11:59:34 UTC]

i tried running gtk, gaim and gedit (the app I know fail) with USE="debug" but they DON'T CRASH ANYMORE! :(
so i re-emerged them without "debug" and they crash again!

here is what i do to exploit the bug
 $ gdb gaim
 gdb> run -d
 [..lots of messages...]

 right click on a contact
 choose "info"
 put your mouse away from the center of the popup
 as soon as the popup appears, move you mouse over the text displayed
 you should see gdb complaining with "Program received signal SIGSEGV, Segmentation fault"

 then run
 gdb> bt full
 gdb> quit

i will now re-emerge the apps with "debug". this will keep me away of these crashes (i hope so)

[Comment 5 Federico Fissore 2006-05-09 12:11:58 UTC]

should I file a bug to gtk+ mantainer?

[Comment 6 Federico Fissore 2006-05-09 12:39:01 UTC]

just to complete: re-emerging ONLY gtk+2.8.17 with USE="debug" fixed the problem

[Comment 7 Federico Fissore 2006-05-12 13:55:05 UTC]

i finally solved the problem using less aggressive CFLAGS
i switched from -O3 to -O2 for the only gtk+ package

sorry about that, anyway

[Comment 8 Olivier Crete (RETIRED) 2006-05-12 14:05:13 UTC]

-O3 is unsafe.. dont use it.. and it many cases it ends up producing slower code then -O2