[Pidgin] #11958: Get Info on contact doesn't work with Gadu-Gadu protocol.

[Pidgin]

#11958: Get Info on contact doesn't work with Gadu-Gadu protocol.
-----------------------------+----------------------------------------------
 Reporter:  diskape          |        Owner:  bartosz  
     Type:  defect           |       Status:  new      
Milestone:  Patches welcome  |    Component:  Gadu-Gadu
  Version:  2.7.0            |   Resolution:           
 Keywords:                   |  
-----------------------------+----------------------------------------------

Comment(by matekm):

 I looked at this and noticed that in linux:

 {{{

 10:58:21) gg: search sequence number: 1295171901
 (10:58:21) gg: ggp_get_info(): Added seq 1295171901(10:58:22) gg: **
 gg_watch_fd(0x871ffe0);

 (10:58:22) gg: ggp_pubdir_reply_handler(): seq 1295171901 --> form
 0x8909e80(10:58:22) gg: ** gg_pubdir50_get(0x890d9a0, 0, "FmStatus");
 }}}


 the seq number is the same when adding to has table and when retrieving
 form from this hash table. On Windows on the other hand:


 {{{
 (18:37:35) gg: search sequence number: 1295113055
 (18:37:35) gg: ggp_get_info(): Added seq 1295113055(18:37:35) gg: **
 gg_watch_fd(00B179E0);

 (18:37:35) gg: ggp_pubdir_reply_handler(): seq 1315784287 --> form
 00000000(18:37:35) g_log: ggp_pubdir_reply_handler: assertion `form !=
 NULL' failed

 }}}

 The seq number used to retrieve form from hash table is different that
 from the one that was used to add it to the hash table.

 I dig little into the code and found that in gg_pubdir50_handle_reply_sess
 function (pubdir50.cc) res->seq = gg_fix32(r->seq);'  - the res->seq is
 set to wrong number. Still not sure if it is root of the problem or why
 only windows builds are affected.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/11958#comment:31>
Pidgin <http://pidgin.im>
Pidgin