Re: [reSIProcate-users] resiprocate access violation crash when getting invite

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

There are a number of header accesses in Dialog::makeRequest it seems it's trapping on one of them.  I don't know of any defects with this function.   If you can trap in the debugger it might help you to track it down further.  Another possibility is that you have customized resip by adding a new Header or parameter definition and have not re-generated the gperf source files - check out:  https://www.resiprocate.org/Adding_a_new_header

For linux builds this happens automatically via Make.  However if you are building on windows you need to do this manually - look at gperf_w32.bat.

Scott

On Tue, Jul 16, 2013 at 4:37 AM, Pornvit Saksobhavivat <tondynamic@xxxxxxxxx> wrote:

Hi,

My company use resiprocate library for communicating with Microsoft LCS server.   It crashes often like once to twice a day on each server.  The stack trace point to when it receive an invite and try to Notify back.  It crashed with access violation exception. Could someone give me a clue what wrong with it?  The stack trace looked like:

> SipGateway.exe!resip::SipMessage::header(const resip::H_Contacts & headerType) Line 1585 C++

  SipGateway.exe!resip::Dialog::makeRequest(resip::SipMessage & request, resip::MethodTypes method) Line 986 C++

  SipGateway.exe!resip::ServerSubscription::makeNotify() Line 333 C++

  SipGateway.exe!resip::ServerSubscription::update(const resip::Contents * document) Line 388 C++

  SipGateway.exe!CEndpoint::sipOnSessionConnected(unsigned long handle_id, int dir, const resip::SipMessage & sipmsg) Line 3224 C++

  SipGateway.exe!ClientInviteSessionHandler::onConnected(resip::Handle<resip::ClientInviteSession> handle, const resip::SipMessage & msg) Line 415 C++

  SipGateway.exe!resip::ClientInviteSession::onConnectedAspect(resip::Handle<resip::ClientInviteSession> c, const resip::SipMessage & msg) Line 1446 C++

  SipGateway.exe!resip::ClientInviteSession::dispatchStart(const resip::SipMessage & msg) Line 738 C++

  SipGateway.exe!resip::ClientInviteSession::dispatch(const resip::SipMessage & msg) Line 401 C++

  SipGateway.exe!resip::Dialog::dispatch(const resip::SipMessage & msg) Line 849 C++

  SipGateway.exe!resip::DialogSet::dispatch(const resip::SipMessage & msg) Line 893 C++

  SipGateway.exe!resip::DialogUsageManager::processResponse(const resip::SipMessage & response) Line 1849 C++

  SipGateway.exe!resip::DialogUsageManager::incomingProcess(std::auto_ptr<resip::Message> msg) Line 1399 C++

  SipGateway.exe!resip::DialogUsageManager::internalProcess(std::auto_ptr<resip::Message> msg) Line 1229 C++

  SipGateway.exe!resip::DialogUsageManager::process(int timeoutMs, resip::Lockable * mutex) Line 1460 C++

  SipGateway.exe!CSipComm::Process() Line 448 C++

  SipGateway.exe!CSipComm::ThreadMemberFunc() Line 459 C++

We use resiprocate 1.6 and it was modified to fit sip messages from LCS.   We also patch some file from 1.7 release in the library too. 

Thank you,

Pornvit

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/