Crash on "msn_soap_read_cb" method ...

Mauro Sérgio Ferreira Brasil mauro.brasil at tqi.com.br
Mon Nov 17 06:32:49 EST 2008


Hi Ka-Hing,

Thank's a lot for your reply.

I'm affraid this issue is not related with our UI, because the crash 
happens on one of the first methods regarding MSN packages handling.
The callstack is as follows:

libmsn.dll!msn_soap_read_cb(void * data=0x073554a0, int fd=2672, 
PurpleInputCondition cond=PURPLE_INPUT_READ)  Line 288 + 0x3 bytes    C
uim.exe!purple_glib_io_invoke(_GIOChannel * source=0x073a6878, 
GIOCondition condition=G_IO_IN, void * data=0x06b79048)  Line 86 + 0x1b 
bytes    C++
purple.dll!g_io_win32_dispatch(_GSource * source=0x0734dc58, int (void 
*)* callback=0x664b88d0, void * user_data=0x06b79048)  Line 514 + 0x15 
bytes    C
libglib-2.0-0.dll!672ddab7()
[Frames below may be incorrect and/or missing, no symbols loaded for 
libglib-2.0-0.dll]
libglib-2.0-0.dll!672dd020()
libglib-2.0-0.dll!672def8b()
libglib-2.0-0.dll!672df16a()
ntdll.dll!7c90104b()
uim.exe!CPurpleService::Run()  Line 792 + 0x6 bytes    C++
libglib-2.0-0.dll!672f7b35()
libgthread-2.0-0.dll!649420da()
msvcrt.dll!77c3a3b0()
kernel32.dll!7c80b683()

Today we received another crash related with new MSN protocol plugin 
(before this issues we were using version 2.4.3 of libpurple with MSN 
version 9 plugin), but now it happened when user tried to move a contact.
Callstack is below:

msvcrt.dll!77c478c0()    
[Frames below may be incorrect and/or missing, no symbols loaded for 
msvcrt.dll]   
libglib-2.0-0.dll!6730c2d3()    
libglib-2.0-0.dll!6730bef0()    
libglib-2.0-0.dll!6730bef0()    
libglib-2.0-0.dll!6730cfb7()    
libglib-2.0-0.dll!67303b44()    
libglib-2.0-0.dll!672e4339()    
libglib-2.0-0.dll!672f3b56()    
libglib-2.0-0.dll!672f3b78()    
libmsn.dll!msn_del_contact_from_group(_MsnSession * session=0x02ccf858, 
const char * passport=0x070662b8, const char * group_name=0x0704e8f8)  
Line 1194 + 0xe bytes    C
libmsn.dll!msn_add_contact_to_group_read_cb(_MsnSoapMessage * 
req=0x02d32438, _MsnSoapMessage * resp=0x07e1b800, void * 
data=0x070557e0)  Line 1033 + 0x10 bytes    C
libmsn.dll!msn_contact_request_cb(_MsnSoapMessage * req=0x02d32438, 
_MsnSoapMessage * resp=0x07e1b800, void * data=0x070557e0)  Line 888 + 
0x9 bytes    C
libmsn.dll!msn_soap_handle_body(_MsnSoapConnection * conn=0x00000000, 
_MsnSoapMessage * response=0x07e1b800)  Line 254    C
libmsn.dll!msn_soap_process(_MsnSoapConnection * conn=0x07efcee0)  Line 
412 + 0x7 bytes    C
libmsn.dll!msn_soap_read_cb(void * data=0x07019a10, int fd=2936, 
PurpleInputCondition cond=PURPLE_INPUT_READ)  Line 303 + 0x6 bytes    C
uim.exe!purple_glib_io_invoke(_GIOChannel * source=0x06fcc048, 
GIOCondition condition=G_IO_IN, void * data=0x071413b0)  Line 86 + 0x1b 
bytes    C++
purple.dll!g_io_win32_dispatch(_GSource * source=0x07015298, int (void 
*)* callback=0x664b88d0, void * user_data=0x071413b0)  Line 514 + 0x15 
bytes    C
libglib-2.0-0.dll!672ddab7()    
libglib-2.0-0.dll!672dd020()    
libglib-2.0-0.dll!672def8b()    
libglib-2.0-0.dll!672df16a()    
libglib-2.0-0.dll!672de0d7()    
uim.exe!CPurpleService::Run()  Line 792 + 0x6 bytes    C++
libglib-2.0-0.dll!672f7b35()    
libgthread-2.0-0.dll!649420da()    

I know this callstacks are not really usefull, but the intention here is 
to point the code location of the errors so maybe you can give us a hint 
considering previous indications or reported tickets.

I hope this info can help you in any way to help me.
Please let me know whether this info is useless, or whether is there any 
other data that I can try to collect here to send you.

Thanks and best regards!
Mauro.




Ka-Hing Cheung escreveu:
> On Fri, 2008-11-14 at 11:05 -0200, Mauro Sérgio Ferreira Brasil wrote:
>   
>> Hello there!
>>
>> The only one reply I received about this issue was regarding the wrong
>> information I've posted.
>> I corrected my first indication informing that the problem happens in
>> fact on line 288 of "soap.c" file from MSN plugin with version 2.5.1
>> of libpurple.
>>
>> The correct block code and line was pointed on my last message too.
>>
>> Considering the first reply asking for the correct information, I was
>> thinking that someone will have a look on this issue and answer
>> something.
>> Even a "this should not happen" or "you should have a look on ticket
>> X", will be very well received, because we are still trying to
>> identificate the origin of this problem, and not a clue until now.
>>
>> Can someone please have a look and help us on that ?
>> Just a litte lead will be enough.
>>     
>
> Do you have some more info other than it crashed on that line?
> Backtrace, debug log? I've never seen a ticket on our side about this,
> so could this be related to your UI?
>
> -khc
>
>
>
>
>
>   

-- 
__At.,                                                                                                                             
   _
 
*Technology and Quality on Information*
Mauro Sérgio Ferreira Brasil
Coordenador de Projetos e Analista de Sistemas
+ mauro.brasil at tqi.com.br <mailto:@tqi.com.br>
: www.tqi.com.br <http://www.tqi.com.br>
( + 55 (34)3291-1700
( + 55 (34)9971-2572

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://pidgin.im/pipermail/devel/attachments/20081117/4121c5e4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CMMI_2.jpg
Type: image/jpeg
Size: 1705 bytes
Desc: not available
URL: <http://pidgin.im/pipermail/devel/attachments/20081117/4121c5e4/attachment-0002.jpg>


More information about the Devel mailing list