pjsip_uri_cmp: uri1's vptr has invalid value exception

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Benny

As requested, I am starting a new thread related to vptr's invalid value

Benny Prijono wrote:
> On Mon, Aug 11, 2008 at 10:30 AM, Pedro Gon?alves 
> <pedro.pandre at gmail.com <mailto:pedro.pandre at gmail.com>> wrote:
>
>     I already added that code; however, now the application is crashing in
>     other place (I guess it's just a matter of time until the assert fails
>     again, and I will send you the log the next time the assert fails), in
>     sip_uri.h's pjsip_uri_cmp(), because uri1's vptr has invalid value
>     (everytime this fails, vptr's value is 0x00000007). If I trace
>     back the
>
>
> I guess that's because the URI value is NULL.
URI? Which URI?
Parameters uri1 and uri2 aren't null.
It's just ((const pjsip_uri*)uri1)->vptr that has an invalid value 
(0x00000007), and it when this exception happens, it always has that 
value(0x00000007).
I've included the stack trace below.
In the stack trace we can see that the received uri1 is, in fact, 
dlg->remote.contact->uri, in pjsip_dlg_on_rx_request().
Any idea why the dialog's remote contact's uri's vptr has such invalid 
value or where it can be changed?


I've attached both the log and the capture I made when this exception 
happened.

>  
>
>
>     stack to mod_ua_on_rx_request, I can see that uri1's vptr already has
>     that invalid value. Any ideas that can help understanding this?
>
>     Here is the stack trace:
>      >    PCCommunicator.exe!pjsip_uri_cmp(pjsip_uri_context_e
>     context=PJSIP_URI_IN_REQ_URI, const void * uri1=0x0c02fd98, const
>     void *
>     uri2=0x0c02fdd0)  Line 275 + 0x13 bytes    C
>         PCCommunicator.exe!pjsip_dlg_on_rx_request(pjsip_dialog *
>     dlg=0x0f89e85c, pjsip_rx_data * rdata=0x0c02f05c)  Line 1545 + 0x2d
>     bytes    C
>
>
> Looking at this stack trace, I couldn't correlate it to the current 
> code, so probably this issue has been fixed recently. It's probably 
> related to this ticket: http://trac.pjsip.org/repos/ticket/580
>
> So could you please update to the latest SVN?
I updated to the latest SVN version, and the stack trace looks similar:
 >    PCCommunicator.exe!pjsip_uri_cmp(pjsip_uri_context_e 
context=PJSIP_URI_IN_REQ_URI, const void * uri1=0x0d9b9d98, const void * 
uri2=0x0d9b9dd0)  Line 275 + 0x13 bytes    C
     PCCommunicator.exe!pjsip_dlg_on_rx_request(pjsip_dialog * 
dlg=0x0fb3c85c, pjsip_rx_data * rdata=0x0d9b905c)  Line 1537 + 0x2d 
bytes    C
     PCCommunicator.exe!mod_ua_on_rx_request(pjsip_rx_data * 
rdata=0x0d9b905c)  Line 682 + 0xd bytes    C
     PCCommunicator.exe!endpt_on_rx_msg(pjsip_endpoint * 
endpt=0x0b8bd05c, int status=0x00000000, pjsip_rx_data * 
rdata=0x0d9b905c)  Line 902 + 0x11 bytes    C
     PCCommunicator.exe!pjsip_tpmgr_receive_packet(pjsip_tpmgr * 
mgr=0x0b50db68, pjsip_rx_data * rdata=0x0d9b905c)  Line 1447 + 0x17 
bytes    C
     PCCommunicator.exe!udp_on_read_complete(pj_ioqueue_key_t * 
key=0x0b50b78c, pj_ioqueue_op_key_t * op_key=0x0d9b9068, long 
bytes_read=0x00000400)  Line 165 + 0x16 bytes    C
     PCCommunicator.exe!ioqueue_dispatch_read_event(pj_ioqueue_t * 
ioqueue=0x0b50b1d8, pj_ioqueue_key_t * h=0x0b50b78c)  Line 550 + 0x16 
bytes    C
     PCCommunicator.exe!pj_ioqueue_poll(pj_ioqueue_t * 
ioqueue=0x0b50b1d8, const pj_time_val * timeout=0x0dc8fcac)  Line 763 + 
0x17 bytes    C
     PCCommunicator.exe!pjsip_endpt_handle_events2(pjsip_endpoint * 
endpt=0x0b8bd05c, const pj_time_val * max_timeout=0x0dc8fe7c, unsigned 
int * p_count=0x00000000)  Line 718 + 0x10 bytes    C
     PCCommunicator.exe!pjsip_endpt_handle_events(pjsip_endpoint * 
endpt=0x0b8bd05c, const pj_time_val * max_timeout=0x0dc8fe7c)  Line 745 
+ 0xf bytes    C
     PCCommunicator.exe!EventHandler(void * __formal=0x00000000)  Line 
630 + 0x16 bytes    C++
     PCCommunicator.exe!thread_main(void * param=0x0b48df94)  Line 413 + 
0x11 bytes    C


Many thanks for all the help
Pedro Gon?alves
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: vptr_invalid_value.log
Url: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080811/bcb52fdd/attachment-0001.pl 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: vptr_invalid_value.pcap
Type: application/octet-stream
Size: 16118 bytes
Desc: not available
Url : http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080811/bcb52fdd/attachment-0001.obj 


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux