Summary: | gaim 0.75-r11 crashes randomly when receiving IMs from specific users | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joe <madCoder> |
Component: | Current packages | Assignee: | Gaim Bugs Crew <gaim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Joe
2004-03-26 23:24:11 UTC
Please obtain a backtrace of the crash, first make sure you have extra debugging turned on when you compile gaim. USE="debug" emerge gaim Backtrace instructions here: http://gaim.sourceforge.net/gdb.php backtrace copied below. This time, while I was waiting for it to segfault, I kept trying to get him to IM me, to see if it would crash. When I went to open an IM window with him to get his attention again, it crashed, which is what makes me think it is a buddy icon problem. Though if that's the case, I can't understand why it works sometimes and not others. (gdb) run Starting program: /usr/bin/gaim Program received signal SIGSEGV, Segmentation fault. 0x4105d860 in ?? () (gdb) bt #0 0x4105d860 in ?? () #1 0x41146909 in std::string::assign(char const*, unsigned) () from /usr/lib/gcc-lib/i586-pc-linux-gnu/3.2.2/libstdc++.so.5 #2 0x411bd91c in acommon::Config::get_default(acommon::ParmString) const () from /usr/lib/libaspell.so.15 #3 0x411bc727 in acommon::Config::retrieve(acommon::ParmString) const () from /usr/lib/libaspell.so.15 #4 0x411b0326 in acommon::find_word_list(acommon::Config*) () from /usr/lib/libaspell.so.15 #5 0x411b241c in acommon::new_speller(acommon::Config*) () from /usr/lib/libaspell.so.15 #6 0x411ad73c in new_aspell_speller () from /usr/lib/libaspell.so.15 #7 0x40f34f36 in init_enchant_provider () from /usr/lib/enchant/libenchant_aspell.so Just a hunch, do you by any chance use gnome and recenctly upgraded to glib/gtk+ 2.4? Yes, actually ... "since I had just installed gnome 2.6, to see if a recompile would fix the problem." It only seemed to start after installing gnome 2.6, which was also when I updated gtk+, glibc, gcc, et al. Would that be an incompatibility issue, something that needs to be fixed, or something that I screwed up with? :o |