Package: jabber Version: 1.4.3-3.3 Severity: important Hello!
Could not determine the reason why segfault occures... It looks like it happens during usuall work - did not find any special conditions. The server goes down very often. I guess it can depend on some specific jabber client. Will try to determine more... Using recent packages from official debian amd64 repository. Dbg output: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47551285660384 (LWP 3040)] 0x00002b3f657e3507 in js_session_to () from ./jsm/jsm.so (gdb) bt #0 0x00002b3f657e3507 in js_session_to () from ./jsm/jsm.so #1 0x00002b3f657f3a89 in mod_offline_out_available () from ./jsm/jsm.so #2 0x00002b3f657f3b1f in mod_offline_out () from ./jsm/jsm.so #3 0x00002b3f657e1e76 in js_mapi_call () from ./jsm/jsm.so #4 0x00002b3f657e313a in _js_session_from () from ./jsm/jsm.so #5 0x000000000040ffb0 in mtq_main () #6 0x00002b3f6504a66b in pth_exit () from /usr/lib/libpth.so.20 #7 0x00002b3f653aeda0 in swapcontext () from /lib/libc.so.6 #8 0x0000000000000000 in ?? () (gdb) Thanks, Andriy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
