Hi, On Tuesday, March 25, 2014 8:46:40 PM UTC+1, Anders Olofsson wrote: > > On 2014-03-23 14:00, Thorsten Bonow wrote: > > It used to happen every time. After the update of the package only one > crash > > occured today on my computer at home (since Friday afternoon). > > Do you know which was the previous version you were using that had the > crash every time? >
don't worry, everything is back to normal :-) On my work machine, the updated Licq crashes reliably a short while after I have sent an ICQ message (message gets through, though). Today I started testing with Jabber, too. This appears to work. > > > 10:59:36.813 [INF] licq: Initializing socket for service 0x10. > > 10:59:36.813 [INF] licq: Requesting service socket for FAM 0x10 > > (#2142/#636)... > > 10:59:36.954 [INF] icq/2: Redirect for service 0x10 received. > > 10:59:36.957 [INF] licq: Connecting to separate server for service 0x10. > > 10:59:36.957 [INF] licq: Connecting to 205.188.17.131:0... > > 11:01:01.317 [INF] icq/2: Sending message through server (#2147). > > 11:01:02.256 [INF] icq/2: Received updated contact information from > server. > > 11:01:44.173 [WAR] licq: Can't establish service 0x10 socket. > > 11:01:44.173 [WAR] licq: Initialization of socket for service 0x10 > > failed, failing event. > > Licq Segmentation Violation Detected. > > The crash is caused by an object being deleted twice. The backtrace only > shows the second time it is deleted, I would like to also find the first > occurance. > I have attached a patch that should make Licq crash on the first delete > instead. Could you please apply it, build Licq, reproduce the fault and > send backtrace.gdb from the crashes. The patch should apply cleanly on > 1.8.0, 1.8.1, or current master as those files haven't changed in a while. > I've applied the patch and rebuild the Debian package. I've attachted the backtrace and the console output generated by starting licq with the '-d15' option. Hope this helps. > There might also be a workaround to avoid the crashes that you can use > until this is fixed. Edit ~./licq/users/<UIN>.ICQ_/<UIN>.conf (where > <UIN> is your account) and set UseBART=0. That should disable the code > where the crash is triggered, however you won't get automatic updates of > profile pictures any longer. Thx. I can live for the moment with Jabber, but will try the workaround if you don't need any more information concerning the crash from me. /Anders > Thx for your help. Toto -- --- You received this message because you are subscribed to the Google Groups "Licq Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to licq-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
07:30:11.822 [INF] icq/2: Spawning daemon threads 07:30:11.980 [INF] licq: Connecting to login server. 07:30:12.176 [INF] licq: Connecting to 64.12.201.165:5190... 07:30:12.499 [INF] icq/2: Requesting logon salt (#7242)... 07:30:12.758 [INF] icq/2: Sending md5 hashed password. 07:30:12.908 [INF] icq/2: Authenticated. Connecting to 64.12.30.51 port 5190. 07:30:12.908 [INF] icq/2: Connecting to 64.12.30.51:5190... 07:30:13.182 [INF] icq/2: Server says he's ready. 07:30:13.183 [INF] icq/2: Sending our channel capability list... 07:30:13.183 [INF] icq/2: Requesting rate info... 07:30:13.322 [INF] icq/2: Server sent us channel capability list (ignoring). 07:30:13.322 [INF] icq/2: Requesting self info. 07:30:13.322 [INF] icq/2: Requesting list rights. 07:30:13.322 [INF] icq/2: Requesting roster rights. 07:30:13.322 [INF] icq/2: Requesting location rights. 07:30:13.322 [INF] icq/2: Requesting contact list rights. 07:30:13.322 [INF] icq/2: Requesting Instant Messaging rights. 07:30:13.322 [INF] icq/2: Requesting BOS rights. 07:30:13.459 [INF] icq/2: Server sent us rate information. 07:30:13.459 [INF] icq/2: Setting ICQ Instant Messaging Mode. 07:30:13.459 [INF] icq/2: Sending capability settings (?) 07:30:13.459 [INF] icq/2: Got Name Info from Server 07:30:13.459 [INF] icq/2: UIN: 70176840 Evil: 0000 07:30:13.550 [INF] icq/2: Server says we are at 80.129.180.139. 07:30:13.551 [INF] icq/2: Server says we're now: Online 07:30:13.596 [INF] icq/2: Got Name Info from Server 07:30:13.597 [INF] icq/2: UIN: 70176840 Evil: 0000 07:30:13.597 [INF] icq/2: Server says we are at 80.129.180.139. 07:30:13.598 [INF] icq/2: Server says we're now: Online 07:30:13.598 [INF] icq/2: Received rights for Location Services. 07:30:13.598 [INF] icq/2: Received rights for Contact List.. 07:30:13.598 [INF] icq/2: Updating contact list (#1946)... 07:30:13.598 [INF] icq/2: Received rights for Instant Messaging.. 07:30:13.598 [INF] icq/2: Received BOS rights. 07:30:13.598 [INF] icq/2: Changing status to Online (#1947)... 07:30:13.598 [INF] icq/2: Sending client ready... 07:30:13.598 [INF] icq/2: Sending offline message request... 07:30:13.598 [INF] icq/2: Server granted contact list rights. 07:30:13.620 [INF] icq/2: Got Master Group record. 07:30:13.620 [INF] icq/2: Got Privacy Setting. 07:30:13.621 [WAR] icq/2: Contact list without request. 07:30:13.622 [INF] icq/2: Received end of contact list. 07:30:13.765 [INF] icq/2: Activating server contact list. 07:30:13.880 [WAR] icq/2: Unknown Buddy Family Subtype: 0001 07:30:13.882 [INF] icq/2: End of Offline messages (nId: 0200). 07:30:13.936 [INF] icq/2: Got Name Info from Server 07:30:13.936 [INF] icq/2: UIN: 70176840 Evil: 0000 07:30:13.937 [INF] icq/2: Server says we are at 80.129.180.139. 07:30:13.937 [INF] icq/2: Server says we're now: Online 07:30:14.015 [WAR] icq/2: Unknown Buddy Family Subtype: 000a 07:30:14.018 [INF] icq/2: root_42 (ICQ_49247365) changed status: Online (v0). 07:30:14.217 [INF] icq/2: Got Name Info from Server 07:30:14.218 [INF] icq/2: UIN: 70176840 Evil: 0000 07:30:14.219 [INF] icq/2: Server says we are at 80.129.180.139. 07:30:14.219 [INF] icq/2: Server says we're now: Online 07:30:36.053 [INF] licq: Initializing socket for service 0x10. 07:30:36.053 [INF] licq: Requesting service socket for FAM 0x10 (#1954/#125)... 07:30:36.327 [INF] icq/2: Redirect for service 0x10 received. 07:30:36.327 [INF] licq: Connecting to separate server for service 0x10. 07:30:36.327 [INF] licq: Connecting to 205.188.17.131:0... 07:32:35.546 [INF] icq/2: Sending message through server (#1958). 07:32:35.808 [INF] icq/2: Received updated contact information from server. 07:32:36.954 [INF] icq/2: Auto response from root_42 (#0). licq: /home/toto/src/debian/licq-1.8.1/src/event.cpp:186: Licq::Event::~Event(): Assertion `myLockCounter == 0' failed. Using gdb to save backtrace to /home/toto/.licq/licq.backtrace.gdb warning: Could not load shared library symbols for linux-gate.so.1. Do you need "set solib-search-path" or "set sysroot"? gdb exited with exit code 0 Backtrace (saved in /home/toto/.licq/licq.backtrace): licq() [0x80c60fa] linux-gate.so.1(__kernel_sigreturn+0) [0xb76e8400] linux-gate.so.1(__kernel_vsyscall+0x10) [0xb76e8424] /lib/i386-linux-gnu/i686/cmov/libc.so.6(gsignal+0x46) [0xb706b4d6] /lib/i386-linux-gnu/i686/cmov/libc.so.6(abort+0x143) [0xb706e853] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x27857) [0xb7064857] /lib/i386-linux-gnu/i686/cmov/libc.so.6(+0x27907) [0xb7064907] licq(_ZN4Licq5EventD2Ev+0x127) [0x8095ed7] /usr/lib/licq/protocol_icq.so(+0x2aa08) [0xb3e06a08] /usr/lib/licq/protocol_icq.so(+0x3da86) [0xb3e19a86] /usr/lib/licq/protocol_icq.so(+0x4602f) [0xb3e2202f] /usr/lib/licq/protocol_icq.so(+0x46230) [0xb3e22230] /usr/lib/licq/protocol_icq.so(+0x8ff58) [0xb3e6bf58] /usr/lib/licq/protocol_icq.so(+0x5ce69) [0xb3e38e69] /usr/lib/licq/protocol_icq.so(+0x658ad) [0xb3e418ad] licq(_ZN10LicqDaemon14PluginInstance16startThreadEntryEPv+0x4b) [0x811f48b] licq() [0x812097d] /lib/i386-linux-gnu/i686/cmov/libpthread.so.0(+0x6ed9) [0xb76a3ed9] /lib/i386-linux-gnu/i686/cmov/libc.so.6(clone+0x5e) [0xb712726e] Attempting to generate core file. Licq has encountered a fatal error. Please report this error either by creating a new ticket at http://trac.licq.org/ or by sending an e-mail to the mailing list licq-dev@googlegroups.com (you must be registered to be able to post, see http://trac.licq.org/wiki/MailingList). To help us debug the error, please include a full description of what you did when the error occurred. Additionally, please include the following files (if they exist): /home/toto/.licq/licq.backtrace /home/toto/.licq/licq.backtrace.gdb Thanks, The Licq Team 07:32:43.633 [WAR] licq: Can't establish service 0x10 socket. 07:32:43.633 [WAR] licq: Initialization of socket for service 0x10 failed, failing event. 07:32:43.633 [INF] licq: Initializing socket for service 0x10. 07:32:43.633 [INF] licq: Requesting service socket for FAM 0x10 (#1960/#131)... Aborted
licq.backtrace
Description: Binary data
licq.backtrace.gdb
Description: Binary data
