Re: [reSIProcate-users] Crash in InterruptStackThread on resip '1.8.6' latest from main
There shouldn't be anything extra required. There was some changes made to the FdPoll stuff on Dec 19th though, so maybe that broke something. Were you previously using an older 1.8 revision that didn't experience this issue? What platform are you running on? Did you happen to grab a stack trace, or log file of this occurring?
Thanks,
Scott
On Sun, Dec 23, 2012 at 4:12 PM, Nauman Sulaiman
<nauman762-home@xxxxxxxxxxx> wrote:
Hi
We have upgraded to resip '1.8.6' ( the latest from main branch as of 20th Dec 2012 not tarball release) from resip 1.7. We are getting a SEG fault (accessing bad pointer)
in Item->processPollEvent in FdPoll.cxx. We are using the recon branch and UserAgent class from this to set up the threads etc.
Is there anything extra that needs setting up with the latest resip stack.
Thanks
void
FdPollGrp::processItem(FdPollItemIf*item, FdPollEventMaskmask)
{
try
{
item->processPollEvent( mask );
}
catch(BaseException& e)
{
// kill it or something?
ErrLog(<<"Exception thrown for FdPollItem: "<< e);
}
item = NULL; // WATCHOUT: item may have been deleted
/*
* If FPEM_Error was reported, should really make sure it was deleted
* or disabled from polling. Otherwise were in stuck in an infinite loop.
* But difficult to do that checking robustly until we serials the items.
*/
}
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/