Hello All,
Does anyone know of a Segmentation Violation bug in sub_alloc() (version )?
I'm not yet sure if this is caused by my application or not. The scenario
is summarized as follows:
1) Create/Register/Subscribe a line (e.g. 1028)
(nua_create/nua_register/nua_subscribe)
2) Make outgoing call
3) Unsubscribe/Unregister/Shutdown the line 1028
4) Create/Register/Subscribe another line (e.g. 10281)
(nua_create/nua_register/nua_subscribe)
5) Make outgoing call
6) Unsubscribe/Unregister/Shutdown the line 10281
7) Create/Register/Subscribe the first line (e.g. 1028)
(nua_create/nua_register/nua_subscribe)
8) Make outgoing call
9) 100 Trying received
10) 180 Ringing received
11) 200 OK received
9) ******* Segmentation Violation in sub_alloc() *******
I think the fault is occurring at the following line (#178):
data = calloc(1, size + MEMCHECK_EXTRA);
Here is the call trace at the time of the Segmentation Violation:
su_base_port_step()
su_poll_port_wait_events()
tport_base_wakeup()
tport_recv_event()
tport_parse()
tport_deliver()
tport_base_deliver()
agent_recv_message()
agent_recv_request()
leg_recv()
incoming_create()
msg_header_copy_as()
msg_header_copy_one_as()
msg_header_alloc()
su_alloc()
sub_alloc()
*** Segmentation Violation ***
Has anyone seen this? Or do you have any insight how my application can
cause this?
Best Regards,
Jerry
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
