On Dec 1, 2007 5:13 AM, Dmitry Teslenko <[EMAIL PROTECTED]> wrote: > Here's results of debugging with gdb: > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -1223964464 (LWP 9850)] > jabber_caps_client_iqcb (js=0x868f258, packet=0x870d138, data=0x871ec58) > at ../../../../libpurple/protocols/jabber/caps.c:440 > 440 ../../../../libpurple/protocols/jabber/caps.c: No such file or > directory. > in ../../../../libpurple/protocols/jabber/caps.c > > > backtrace: > #0 jabber_caps_client_iqcb (js=0x868f258, packet=0x870d138, > data=0x871ec58) > at ../../../../libpurple/protocols/jabber/caps.c:440 > #1 0xb66634a2 in jabber_iq_parse (js=0x868f258, packet=0x870d138) > at ../../../../libpurple/protocols/jabber/iq.c:324 > #2 0xb666c39f in jabber_process_packet (js=0x868f258, packet=0xbff9e0ec) > at ../../../../libpurple/protocols/jabber/jabber.c:197 > #3 0xb666f589 in jabber_parser_element_end_libxml (user_data=0x868f258, > element_name=0x86c86ac "iq", prefix=0x0, > namespace=0x86c8643 "jabber:client") > at ../../../../libpurple/protocols/jabber/parser.c:116 > #4 0xb751132d in ?? () from /usr/lib/libxml2.so.2 > #5 0x0868f258 in ?? () > #6 0x086c86ac in ?? () > #7 0x00000000 in ?? () > > Pidgin (gaim) worked for me for year or more without modifications of > configuration and recently (yestarday or so) I've got that crash. > > Please, help to find out what's problem. > > Its pidgin 2.2.1 @ ubuntu 7.10 >
I'm pretty sure you're running into something like http://developer.pidgin.im/ticket/4081 -D
_______________________________________________ Support mailing list [email protected] http://pidgin.im/cgi-bin/mailman/listinfo/support
