[OpenSER-Users] help.. openser 1.3.0 crash -- presence/ BLA

[Zahid Mehmood]

Hi Anca,
    Thank you for your quick response.  Attached below is the  
information you requested.

Thanks.

-- 
Zahid


(gdb) bt
#0  0x00b3bba3 in strncmp () from /lib/tls/libc.so.6
#1  0x00140bcb in get_dialog (dialog=0xb60fe518, hash_code=22) at  
hash.c:289
#2  0x0014ae10 in subs_cback_func (t=0xb61210b0, cb_type=256,  
ps=0xdb6314) at send_subscribe.c:248
#3  0x00d945b2 in run_trans_callbacks (type=256, trans=0xb61210b0,  
req=0x0, rpl=0xffffffff, code=408) at t_hooks.c:205
#4  0x00da14ca in local_reply (t=0xb61210b0, p_msg=0xffffffff,  
branch=0, msg_status=408, cancel_bitmap=0xbfe95834)
     at t_reply.c:1255
#5  0x00da5f4c in timer_routine (ticks=89623, attr=0x0) at timer.c:254
#6  0x080b403f in start_timer_processes () at timer.c:275
#7  0x08066d60 in main (argc=1, argv=0xbfe95a94) at main.c:873


(gdb) f 1
#1  0x00140bcb in get_dialog (dialog=0xb60fe518, hash_code=22) at  
hash.c:289
289	hash.c: No such file or directory.
	in hash.c


(gdb) p *dialog
$1 = {id = {s = 0x0, len = 0}, pres_uri = 0xb60fe5a0, event = 4,  
expires = 0, desired_expires = 1203116204, flag = 4,
   db_flag = 0, cb_param = 0x0, next = 0x0, ua_flag = 0, etag = {s =  
0x0, len = 0}, tuple_id = {s = 0x0, len = 0},
   body = 0x0, content_type = {s = 0x0, len = 0}, watcher_uri =  
0xb60fe5bf, call_id = {s = 0x0, len = 0}, to_tag = {s = 0x0,
     len = 0}, from_tag = {s = 0x0, len = 0}, cseq = 0, version = 0,  
watcher_count = 0, outbound_proxy = 0x0,
   extra_headers = 0x0, record_route = {s = 0x0, len = 0}, contact =  
{s = 0xb60fe5de "sip:10563 at 10.0.0.129", len = 23}}


(gdb) p *p
$2 = {id = {s = 0x0, len = 0}, pres_uri = 0xb60ff430, event = 4,  
expires = 1203116184, desired_expires = 1203116174,
   flag = 4, db_flag = 1, cb_param = 0x0, next = 0x0, ua_flag = 0,  
etag = {s = 0x0, len = 0}, tuple_id = {s = 0x0, len = 0},
   body = 0x0, content_type = {s = 0x0, len = 0}, watcher_uri =  
0xb60ff44f, call_id = {
     s = 0xb60ff46e "7bfbf09e-25540 at 10.0.0.1298A33FF0F-5628642A533cb9e91f4b999cf76861cbb9ed54ed-3d24sip 
:10563 at 10.0.0.129t.columbia.edu\">\n</dialog-info>\n??\017?&", len =  
28}, to_tag = {
     s = 0xb60ff48a  
"8A33FF0F-5628642A533cb9e91f4b999cf76861cbb9ed54ed-3d24sip:10563 at 10.0.0.129t.columbia.edu 
\">\n</dialog-info>\n??\017?&", len = 17}, from_tag = {
     s = 0xb60ff49b "533cb9e91f4b999cf76861cbb9ed54ed-3d24sip:10563 at 10.0.0.129t.columbia.edu 
\">\n</dialog-info>\n??\017?&", len = 37}, cseq = 21, version = 0,  
watcher_count = 0, outbound_proxy = 0x0, extra_headers = 0x0,  
record_route = {s = 0x0,
     len = 0}, contact = {s = 0xb60ff4c0 "sip:10563 at 10.0.0.129t.columbia.edu 
\">\n</dialog-info>\n??\017?&", len = 23}}


(gdb)

On Feb 21, 2008, at 3:57 AM, Anca Vamanu wrote:

> Hi Zahid,
>
> If you still got the core, please run a print for '*dialog' and '*p'  
> variables in frame 1 of the gdb backtrace and send the result.
>
> Thanks and regards,
> Anca Vamanu
>
> Zahid Mehmood wrote:
>> Hi All,
>>     I need help with troubleshooting openser 1.3.0 crash. I am   
>> running openser 1.3.0 (not from svn) to provide only BLA presence   
>> service.  The config file is based on the sample provided on  
>> openser  website.
>>
>> This is the first time openser actually crashed.  Twice before it   
>> stopped working but the process never died.
>>
>>
>> Originally openser was running with debug=3.  I have changed it to  
>> log  more information now.   What else can i do to generate more  
>> useful  information to help resolve this issue?
>>
>> Thanks in advance for your help!
>>
>>
>