Crash when moving buddies

[johnw42]

I got this stack trace right after moving "shponglespore@…" in my buddy list. I moved out out of a group, causing a "general" group to be created.

#0  0x0045d402 in __kernel_vsyscall ()
#1  0x009fa1f8 in raise () from /lib/libc.so.6
#2  0x009fb948 in abort () from /lib/libc.so.6
#3  0x080a25d9 in sighandler (sig=11) at gtkmain.c:212
#4  <signal handler called>
#5  0x0020d346 in g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
#6  0x002d05a0 in purple_presence_get_status (presence=0x95e4c18,
    status_id=0x7f85963 "dnd") at status.c:1439
#7  0x002c59ad in purple_prpl_got_user_status (account=0x9552cc0,
    name=0x97a9f90 "shponglespore@gmail.com", status_id=0x7f85963 "dnd") at prpl.c:147
#8  0x07f80e2b in jabber_presence_parse (js=0x96f7ea8, packet=0x9715db8)
    at presence.c:561
#9  0x07f7bc72 in jabber_process_packet (js=0x96f7ea8, packet=0x9715db8) at jabber.c:187
#10 0x07f7fcdd in jabber_parser_element_end_libxml (user_data=0x96f7ea8,
    element_name=0x97afcaf "presence", prefix=0x0, namespace=0x97afb33 "jabber:client")
    at parser.c:116
#11 0x067342e6 in xmlSkipBlankChars () from /usr/lib/libxml2.so.2
#12 0x06740045 in xmlParseChunk () from /usr/lib/libxml2.so.2
#13 0x07f7fda3 in jabber_parser_process (js=0x96f7ea8,
    buf=0x7f88d40 "<presence from=\"shponglespore@gmail.com/workFEC54E8B\" to=\"shponglespore2@gmail.com/workCBB100DD\"><show>dnd</show><status>At work.</status><c node=\"http://pidgin.im/caps\" ver=\"2.0.0\" xmlns=\"http://jabb"..., len=277) at parser.c:192
#14 0x07f79e6f in jabber_recv_cb_ssl (data=0x96f7e58, gsc=0x978a700,
    cond=PURPLE_INPUT_READ) at jabber.c:388
#15 0x002d2043 in recv_cb (data=0x95e4c18, source=16, cond=PURPLE_INPUT_READ)
    at sslconn.c:138
#16 0x0809138f in pidgin_io_invoke (source=0x9794a08, condition=G_IO_IN, data=0x979de10)
    at gtkeventloop.c:77
#17 0x0023f3ac in g_vasprintf () from /usr/lib/libglib-2.0.so.0
#18 0x002193ee in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#19 0x0021c3f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#20 0x0021c6e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#21 0x007e51b5 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#22 0x080a310d in main (argc=1, argv=0xbf7fe7d4) at gtkmain.c:841

After restarting Pidgin and trying to reconnect, I got this stack trace, similar to those in ticket #660:

#0  0x00db4402 in __kernel_vsyscall ()
#1  0x0044e1f8 in raise () from /lib/libc.so.6
#2  0x0044f948 in abort () from /lib/libc.so.6
#3  0x080a25d9 in sighandler (sig=11) at gtkmain.c:212
#4  <signal handler called>
#5  purple_status_get_type (status=0x27) at status.c:905
#6  0x002cf1f5 in purple_status_is_online (status=0x27) at status.c:971
#7  0x002d0779 in purple_presence_is_online (presence=0xa151b68) at status.c:1491
#8  0x08071abf in buddy_is_displayable (buddy=0xa151a60) at gtkblist.c:2561
#9  0x08076fdc in pidgin_blist_update_contact (list=0x0, node=Variable "node" is not available.
) at gtkblist.c:4971
#10 0x08076cdd in pidgin_blist_update (list=0x0, node=0xa151958) at gtkblist.c:5109
#11 0x08078252 in do_selection_changed (new_selection=0xa151958) at gtkblist.c:4687
#12 0x0021af06 in g_main_context_wakeup () from /usr/lib/libglib-2.0.so.0
#13 0x002193ee in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0x0021c3f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#15 0x0021c6e3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#16 0x0087b1b5 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#17 0x080a310d in main (argc=1, argv=0xbf869c84) at gtkmain.c:841

Finally, I should point out that the URLs in this error message are broken:

Pidgin has segfaulted and attempted to dump a core file.
This is a bug in the software and has happened through
no fault of your own.

If you can reproduce the crash, please notify the Pidgin
developers by reporting a bug at
http://pidgin.im/bug.php

Please make sure to specify what you were doing at the time
and post the backtrace from the core file.  If you do not know
how to get the backtrace, please read the instructions at
http://pidgin.im/gdb.php

If you need further assistance, please IM either SeanEgn or
LSchiere (via AIM).  Contact information for Sean and Luke
on other protocols is at
http://pidgin.im/contactinfo.php

[johnw42]

One more thing--this problem went away on its own after restarting Pidgin a few times.

[nwalp]

This should now be fixed in mtn, and will be fixed for 2.0.1.