[SR-Users] FW: (Devel) Segmentation fault using pua_dialoginfo

[Daniel-Constantin Mierla]

Hello,

interesting that the output of bt shows inline core_hash function 
prototype with same parameters as publ_cback_func, not being able to 
spot eventual wrong parameter values.

Anyhow, in the gdb, can you do the commands:

frame 1
p *hentity

and send the output? Let's see the value of the pub uri for which 
hashing function crashes.

What are the parameters for pua and pua_dialog info you set in the 
config file?

Cheers,
Daniel

On 5/15/12 11:53 AM, Charles Chance wrote:
>
> Hi Daniel,
>
> As per your previous reply (sorry, I deleted it accidentally), please 
> find attached output of 'bt full' as requested.
>
> Best regards and thanks again,
>
> Charles
>
> ------------------------------------------------------------------------
>
> *From:*Charles Chance [mailto:charles.chance at sipcentric.com]
> *Sent:* 13 May 2012 11:21
> *To:* 'SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) 
> -Users Mailing List'
> *Subject:* (Devel) Segmentation fault using pua_dialoginfo
>
> Hi,
>
> Currently testing devel version and experiencing the following when 
> using pua_dialoginfo:
>
> -------------------------------------
>
> Program terminated with signal 11, Segmentation fault.
>
> #0  core_hash (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at 
> ../../hashes.h:279
>
> 279 v=(*p<<24)+(p[1]<<16)+(p[2]<<8)+p[3];
>
> (gdb) bt
>
> #0  core_hash (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at 
> ../../hashes.h:279
>
> #1  publ_cback_func (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at 
> send_publish.c:246
>
> #2  0x002861d6 in run_trans_callbacks_internal (cb_lst=0xb3d7e370, 
> type=1024, trans=0xb3d7e330, params=0xbfcc31c8) at t_hooks.c:290
>
> #3  0x002864d6 in run_trans_callbacks (type=1024, trans=0x200, 
> req=0x0, rpl=0xb7bea008, code=200) at t_hooks.c:317
>
> #4  0x002afb28 in local_reply (t=0xb3d7e330, p_msg=0xb7bea008, 
> branch=0, msg_status=200, cancel_data=0xbfcc345c) at t_reply.c:2001
>
> #5  0x002b2b45 in reply_received (p_msg=0xb7bea008) at t_reply.c:2350
>
> #6  0x0809d5f4 in forward_reply (msg=0xb7bea008) at forward.c:790
>
> #7  0x080e11a9 in receive_msg (
>
>     buf=0x82c4fa0 "SIP/2.0 200 OK\r\nVia: SIP/2.0/UDP 
> xx.xx.xx.xxx;branch=z9hG4bKc13b.25313b6.0\r\nTo: 
> sip:000094 at xx.xx.xx.xxx;tag=03373b1b433b65504ea28bd3d9e6db76.d7f2\r\nFrom: 
> sip:000094 at xx.xx.xx.xxx;tag=4cc17c2c75cb82fa"..., len=393, 
> rcv_info=0xbfcc3648) at receive.c:270
>
> #8  0x0817801b in udp_rcv_loop () at udp_server.c:544
>
> #9  0x080b0426 in main_loop () at main.c:1633
>
> #10 0x080b3d02 in main (argc=11, argv=0xbfcc3924) at main.c:2546
>
> (gdb) up
>
> #1  publ_cback_func (t=0xb3d7e330, type=1024, ps=0xbfcc31c8) at 
> send_publish.c:246
>
> 246 hash_code= core_hash(hentity->pres_uri, NULL, HASH_SIZE);
>
> (gdb) p hentity->pres_uri
>
> Cannot access memory at address 0x8
>
> (gdb) p *hentity
>
> Cannot access memory at address 0x0
>
> -------------------------------------
>
> Your time is greatly appreciated...
>
> Charles
>

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20120515/db7a0c48/attachment.htm>