Summary: | Centericq Segmentation Fault during MSN Login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Victor Nawothnig <victor.nawothnig> |
Component: | Current packages | Assignee: | Wolfram Schlich (RETIRED) <wschlich> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | david, denilsonsa, net-im, phrexianreaper, tobias.pal |
Priority: | Normal | ||
Version: | 2005.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Valgrind output from another machine of mine |
Description
Victor Nawothnig
2006-04-27 04:01:01 UTC
Confirmed. Same happens on a machine of mine. dump obtained from `centericq -d` MSN::ext::gotBuddyListInfo [OUT] CHG 4 IDL 0 + 08:27 [msn] logged in [IN] MSG Hotmail Hotmail 219 MSN::ext::gotInitialEmailNotification + 08:27 [msn] unread e-mail: 0 in inbox, 3 in folders [IN] NOT 325 <<borkage occurs here>> Segmentation fault chris@shell ~ $ Error does not occur anymore since I unticked the option 'Check local mailbox' once. (Ticked it again) Now centericq segfaults when I quit it using the q-Key. Version hasnt been changed, config hasnt been changed. (In reply to comment #2) > Error does not occur anymore since I unticked the option 'Check local mailbox' > once. (Ticked it again) > Now centericq segfaults when I quit it using the q-Key. > Version hasnt been changed, config hasnt been changed. > I've always had that turned off. Moving ~/.centericq to another folder then recreating the config causes the error to occur again on login. I do not believe this is config related. Please try the source once. If the error still occurs use valgrind to bugtrace the segmentation fault. Created attachment 87315 [details]
Valgrind output from another machine of mine
Tested source on another machine of mine, with same results. Attaching valgrind output.
Id like you to post your emerge --info also, if you dont mind, since the valgrind output looks a bit useless to me, at least. (In reply to comment #6) > Id like you to post your emerge --info also, if you dont mind, > since the valgrind output looks a bit useless to me, at least. > Sure thing. Would gdb show anything significant? # emerge --info Portage 2203-svn (default-linux/x86/2005.1, gcc-3.4.5, glibc-2.3.6-r3, 2.6.13-gentoo-r5 i686) ================================================================= System uname: 2.6.13-gentoo-r5 i686 Pentium III (Katmai) Gentoo Base System version 1.6.14 distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] dev-lang/python: 2.3.5, 2.4.2 dev-python/pycrypto: [Not Present] dev-util/ccache: [Not Present] dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.12 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-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium3 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distcc distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirror.datapipe.net/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync/portage/" USE="x86 aim apm audiofile avi berkdb bitmap-fonts bzip2 cli client-only crypt cups curl dedicated dri eds emboss encode expat foomaticdb fortran gdbm gif gmp gpm gstreamer gtk2 icq imap imlib isdnlog jabber java jpeg ldap libg++ libwww lj mad mikmod motif mp3 mpeg msn ncurses nls ogg oggvorbis oscar oss pam pcre pdflib perl png pppd python qt quicktime readline reflection ruby sdl session spell spl ssl tcpd truetype truetype-fonts type1-fonts udev usb vorbis xml2 xorg yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, INSTALL_MASK, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTAGE_RSYNC_EXTRA_OPTS, PORTAGE_RSYNC_OPTS I had the same problem, however it doesn't show itself when I recompiled for debugging. It seems that stepping down optimisation to -O0 stops it segfaulting for me, try it and see if that helps. Oops. After a day of testing where it was fine, I have now connected again and it has segfaulted. Annoyingly, I had removed all debug symbols from the binary by this point! This could well be to do with certain contacts being online, I will have to try again another day. This bug affects me as well. I have found a debian changelog[1] which says: --- centericq (4.21.0-8) unstable; urgency=low * Update libmsn to last version : 3.2. This update can fix msn connection problem for some users. -- Julien Lemoine <speedblue@debian.org> Sat, 17 Dec 2005 11:00:01 +0100 --- in centericq_4.21.0-11.diff.gz there is: "## DP: apply patch to update libmsn to lost version (3.2)" but I'm not familiar with this patching stuff. Hope it will help. Have a nice day, Bud [1]http://packages.debian.org/changelogs/pool/main/c/centericq/centericq_4.21.0-11/changelog Upstream does not care about CenterICQ, so I don't either :-( Maybe we should hard-mask and then remove CenterICQ from Portage. I don't see a chance of upstream changing behavior. This is frustrating to me as it is to all users experiencing problems with CenterICQ. Resolving as WONTFIX as long as nobody else is willing to step in and deal with this upstream situation. Guys, in http://centericq.de/#754 you can find a patch that solves that problem in Centericq.. I don't know how to patch an ebuild or even the portage tree, so I hope someone does that.. Thanks. (In reply to comment #13) > Guys, in http://centericq.de/#754 you can find a patch that solves that problem > in Centericq.. I tried it, and at first it failed patching. Then I did: sed 's,/libmsn/,/libmsn-0.1/,g' on patch file, and finally the patch worked. I tried to compile it with patch, and it did not segfaulted. I suggest adding a -r3 centericq version with above patch applied. *** Bug 161847 has been marked as a duplicate of this bug. *** *** Bug 161847 has been marked as a duplicate of this bug. *** |