On Sat, May 31, 2008 at 6:43 PM, Norman W. Franke <norman at myasd.com> wrote: > On May 31, 2008, at 1:40 PM, Norman Franke wrote: > > On our production systems, we are getting some crashes like this: > #0 0x00295108 in pjsua_call_on_media_update > #1 0x002c79f4 in inv_negotiate_sdp > #2 0x002c9810 in inv_check_sdp_in_incoming_msg > #3 0x002ca128 in inv_on_state_early > #4 0x002c7770 in mod_inv_on_tsx_state > #5 0x002b4b14 in pjsip_dlg_on_tsx_state > #6 0x002b9218 in tsx_set_state > #7 0x002ba22c in tsx_on_state_proceeding_uac > #8 0x002b9374 in pjsip_tsx_recv_msg > #9 0x002bb334 in mod_tsx_layer_on_rx_response > #10 0x00285d8c in endpt_on_rx_msg > #11 0x002b10f0 in pjsip_tpmgr_receive_packe > #12 0x002d2198 in udp_on_read_complete > #13 0x002ada30 in ioqueue_dispatch_read_event > #14 0x002ae398 in pj_ioqueue_poll > #15 0x00285958 in pjsip_endpt_handle_events2 > #16 0x0028e56c in pjsua_handle_events > #17 0x0028e5c8 in worker_thread > #18 0x0028372c in thread_main > #19 0x9002bd08 in _pthread_body > I'll attempt to do both -O2 and -g to see if I can get some better stack > traces. (I have to do -O2, or I get some glitches on some rather slow > iMacs.) All I can say for now is this looks to have something to do with processing SDP in the response. If you have the message logging that could be helpful. Cheers Benny
