On Sat, Jul 06, 2002 at 12:53:36PM +0200, Stefan Seifert wrote: > gfdsa wrote: > > >Hi. > > > >Does anyone can give me a clue? > >It will be very appreciated > > > >#define KDE_VERSION_STRING "3.0.0" > >qt - 3.0.4 > >licq-20020705 > > > >04:42:37: [WRN] Licq: Ignoring stale lockfile (pid 6214) > >Licq Segmentation Violation Detected. > >Backtrace: > >licq(licq_handle_sigsegv+0x77) [0x809dceb] > >/lib/libpthread.so.0 [0x4acc70d4] > >/lib/libc.so.6 [0x4ad8a768] > >/lib/libc.so.6(__libc_free+0x8f) [0x4add0a3b] > >/usr/X11R6/lib/X11/locale/common/ximcp.so.2(_XimCheckIfLocalProcessing+0x59) > >[0x507e5d8d] > >/usr/X11R6/lib/X11/locale/common/ximcp.so.2(_XimOpenIM+0x256) [0x507e5712] > >/usr/X11R6/lib/libX11.so.6 [0x4b29aafd] > >/usr/X11R6/lib/X11/locale/common/ximcp.so.2(_XimRegisterIMInstantiateCallback+0xc9) > >[0x507e4ddd] > >/usr/X11R6/lib/libX11.so.6 [0x4b29ac51] > >/usr/X11R6/lib/libX11.so.6(XRegisterIMInstantiateCallback+0x48) > >[0x4b27d254] > >/usr/qt/3/lib/libqt-mt.so.3(qt_init_internal__FPiPPcP9_XDisplayUlUl+0x1c7f) > >[0x4b45db47] > >/usr/qt/3/lib/libqt-mt.so.3(qt_init__FPiPPcQ212QApplication4Type+0x28) > >[0x4b45e36c] > >>/usr/qt/3/lib/libqt-mt.so.3(construct__12QApplicationRiPPcQ212QApplication4Type+0x67) > > >[0x4b4afd3f] > >/usr/qt/3/lib/libqt-mt.so.3(__12QApplicationRiPPcb+0x5e) [0x4b4afbe2] > >/usr/kde/3/lib/libkdecore.so.4(__12KApplicationRiPPcRC8QCStringbT4+0x2d) > >[0x4bba0549] > >/usr/local/lib/licq/licq_kde-gui.so(__8CLicqGuiiPPc+0x4b) [0x4aee00db] > >/usr/local/lib/licq/licq_kde-gui.so(LP_Main+0x44) [0x4aedf954] > >/usr/local/lib/licq/licq_kde-gui.so(LP_Main_tep+0x21) [0x4aedf645] > >/lib/libpthread.so.0 [0x4acc427c] > >/lib/libc.so.6(__clone+0x3a) [0x4ae3430a] > >Attempting to generate core file. > > > > > > > I had the same problem. In the Bugtracker on Sourceforge.net I found the > hint to start licq with > KMALLOC=0 licq > on the shell, this way it works just fine. > > Does anyone know something about that and a better solution? Otherwise > it should at least be noted in some docs.
For me, XIM-related crashes started appearing only when I upgraded to Qt 3.0.4 and KDE 3.0.2. Since they don't appear in a Qt-only licq, I assume KDE 3.0.2 is to blame. Did KDE 3.0.2 introduce changes in the optimized malloc? Or maybe 3.0.1 for Debian was compiled without the optimized malloc? In any case, I'd rather see it fixed than telling users to disable it. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Got root? We do. http://thinkgeek.com/sf _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
