licq CVS has been very unstable since about February 2002. I usually get a segfault every 1 or 2 days, and my friends have the same experience. Is it stable for everyone else, or is it just something you don't talk about? I know that a CVS release is expected to be buggy, but I consider this to be a special case because no stable and working release of licq exists atm. Also, these segfaults have been around for many months but nobody seems to talk about them.
It runs and works fine, and then it'll suddenly crash for no appearent reason. Looking at the patterns over the last few months it seems that it's related to someone communicating with me over a direct connection, e.g. to check my status or send me a message. Because it usually takes many hours for this to happen, and it seems quite random, I cannot easily reproduce it. So I'd like to know what I can do to help diagnose it. strace, gdb, or something else? So far I just have a stack trace from the last crash: Licq Segmentation Violation Detected. Backtrace: licq(licq_handle_sigsegv+0x84) [0x809d514] /lib/libpthread.so.0(sigaction+0x19b) [0x4011c47b] /lib/libc.so.6(killpg+0x48) [0x401d9128] /lib/libc.so.6(__libc_free+0xc4) [0x4022a354] licq(_._10CPacketTcp+0x29) [0x8068339] licq(ProcessTcpPacket__10CICQDaemonP9TCPSocket+0x1de8) [0x8075918] licq(MonitorSockets_tep__FPv+0x541) [0x80803e1] /lib/libpthread.so.0(pthread_detach+0x1137) [0x40119b07] /lib/libc.so.6(__clone+0x3a) [0x4029146a] Attempting to generate core file. _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
