Richard Allen spake unto us the following wisdom: > > Expect gdb backtraces the next time this happens :) > > Got them. And things look a bit diffrent: > #8 0x00007f0d7132bade in sipe_backend_transport_flush () from > /usr/lib64/purple-2/libsipe.so > #9 0x00007f0d71306230 in sipe_core_deallocate () from > /usr/lib64/purple-2/libsipe.so > #10 0x00007f0d712f3dc2 in sipe_purple_close () from > /usr/lib64/purple-2/libsipe.so
Unfortunately, Pidgin-SIPE is an unsupported third party plugin. Without looking too closely, I'm guessing there's an error on the socket and it's not handling that gracefully. > I did a few contiune's and ctrl+c's but always the same bt. > > Step 0 lists fd 17: > > [ra@hamburger ~]$ ll /proc/2863/fd/17 > lrwx------. 1 ra ra 64 May 14 00:04 /proc/2863/fd/17 -> socket:[155804] > > This time a socket which makes more sense. the last time I checked > what the fd was pidgin had already recovered so perhaps some fd's had > been closed and reopened throwing off the numbers? Yes, it makes much more sense. I suspect your analysis is correct. Ethan _______________________________________________ Support@pidgin.im mailing list Want to unsubscribe? Use this link: http://pidgin.im/cgi-bin/mailman/listinfo/support
