Re: backtrace
Pekka Riikonen <[email protected]> Sat, 1 Sep 2007 10:53:37 +0200 (CEST)
| Newsgroups | gmane.network.silc.devel |
|---|---|
| Message-ID | <[email protected]> |
: #0 0xb7d7a01f in � () from /lib/i686/cmov/libpthread.so.0 : #1 0xb7604b95 in silc_rwlock_wrlock (rwlock=0x0) at silcunixthread.c:217 : #2 0xb769c635 in silc_client_notify_join (fsm=0x8c485a8, : fsm_context=0x8c50880, state_context=0x8c43a98) at client_notify.c:401 : #3 0xb7612644 in silc_fsm_continue_sync (fsm=0x8c485a8) at silcfsm.c:429 : #4 0xb76940f4 in silc_client_get_clients_cb (client=0x819fab8, : conn=0x8c50880, command=1 '\001', status=54 '6', error=54 '6', : context=0x8c6e338, ap=0xbfdb0004 "") at client_entry.c:221 : #5 0xb769f81c in silc_client_command_callback (cmd=0x8c441a8) : at command_reply.c:92 : #6 0xb76a5988 in silc_client_command_reply_whois (fsm=0x8c441b0, : fsm_context=0x8c441a8, state_context=0x8bdbcb8) at command_reply.c:422 : #7 0xb7612644 in silc_fsm_continue_sync (fsm=0x8c441b0) at silcfsm.c:429 : This happens because the WHOIS query during JOIN notify timed out, and the reprocessing of the JOIN notify didn't handle the timeout correctly and unreferenced the client entry untill it became free memory. The latest commits should fix this problem. Pekka ________________________________________________________________________ Pekka Riikonen priikone at silcnet.org Secure Internet Live Conferencing (SILC) http://silcnet.org/ _______________________________________________________________________ Info: https://lists.silcnet.org/mailman/listinfo/silc-announce Archive: https://lists.silcnet.org/pipermail/silc-announce FAQ: http://silcnet.org/support/faq/