[Pidgin] #1989: Segmentation fault in jabber protocol plugin

[Pidgin]

#1989: Segmentation fault in jabber protocol plugin
-----------------------+----------------------------------------------------
 Reporter:  snakeru    |       Type:  patch
   Status:  new        |   Priority:  minor
Component:  libpurple  |    Version:  2.0.2
 Keywords:             |    Pending:  0    
-----------------------+----------------------------------------------------
 I am using libpurple (in fact gaim beta6, but libpurple do not have these
 checks either) in my application and after move to another OS (Debian
 sarge > Debian etch) I have started experiencing these segfaults:
 {{{
 #0  jabber_buddy_find (js=0x0, name=0xb50bddb4 "xxxx at gmail.com", create=1)
 at buddy.c:71
 #1  0xb5235e85 in jabber_message_send_im (gc=0x92b5b10, who=0xb50bddb4
 "xxxx at gmail.com",
     msg=0xb4fcd7a4 "xxxx at gmail.com, this is my IM Page on SNIMMER. You can
 chat with me there: http://xxxx.snimmer.com/", flags=0) at message.c:497
 #2  0xb550d57b in serv_send_im (gc=0x92b5b10, name=0xb50bddb4
 "xxxx at gmail.com",
     message=0xb4fcd7a4 "xxxx at gmail.com, this is my IM Page on SNIMMER. You
 can chat with me there: http://xxxx.snimmer.com/", flags=0) at
 server.c:135
 #3  0xb5566f9b in pygaim_server_serv_send_im (self=0x0, args=0xb583c5a4)
 at generated.c:5632
 #4  0xb5948ab9 in ?? ()
 #5  0x00000000 in ?? ()
 }}}
 after adding a check to jabber_buddy_find I got this also:
 {{{
 #0  jabber_get_next_id (js=0x0) at jabber.c:1056
 #1  0xb51d1ed8 in jabber_message_send_im (gc=0x92a7b00,
     who=0xb4f6a1bc "xxxx at gmail.com",
     msg=0xb5078e8c "xxxx, this is my IM Page on SNIMMER. You can chat with
 me there: http://xxxx.snimmer.com/", flags=0) at message.c:513
 #2  0xb54a957b in serv_send_im (gc=0x92a7b00, name=0xb4f6a1bc
 "xxxx at gmail.com",
     message=0xb5078e8c "xxxx, this is my IM Page on SNIMMER. You can chat
 with me there: http://xxxx.snimmer.com/", flags=0) at server.c:135
 #3  0xb5502f9b in pygaim_server_serv_send_im (self=0x0, args=0xb57d85a4)
 at generated.c:5632
 #4  0xb58d77e1 in ?? ()
 #5  0x00000000 in ?? ()
 }}}
 I know - it is probably my fault that message is being sent over dead
 connection in the first place but it is probably still a good idea to have
 check if (!js) return; in jabber_buddy_find and jabber_get_next_id.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/1989>
Pidgin <http://pidgin.im>
Pidgin