From: Aleksandar K. <ki...@ar...> - 2006-06-15 10:10:12
|
On Thu, 15 Jun 2006 11:58:50 +0200 Rudo Thomas <ru...@ma...> wrote: > No :) I got to work, found licq crashed, ran it again, tried to change > status to Online. BOOM. So it's the same UIN I have been happily using > for a few months now. Same here ! The same thing, happened today for the first time. And I was NOT trying to register a new ICQ account, it just crashed out of the blue and I can't run it anymore, it crashes every time I try to log-on to server. And that's Licq that I've been running for more months with no problems, version 1.3.2 from debian package, now I tried to upgrade to 1.3.2-6 but it also crashes, the same way Licq Segmentation Violation Detected. Backtrace: licq(licq_handle_sigsegv+0xe6) [0x80f9116] [0xffffe420] licq(_ZN10CICQDaemon16ProcessNewUINFamER7CBuffert+0x12b) [0x80c548b] licq(_ZN10CICQDaemon18ProcessDataChannelER7CBuffer+0x18e) [0x80c5b3e] licq(_ZN10CICQDaemon16ProcessSrvPacketER7CBuffer+0x1e7) [0x80ba767] licq(_Z18MonitorSockets_tepPv+0x64c) [0x80c7d8c] /lib/tls/libpthread.so.0 [0xb7dc0ced] /lib/tls/libc.so.6(__clone+0x5e) [0xb7c52dee] |