Re: [recon-devel] Asserts in current testUA/Recon/Resip from svn revision 8401
Are these issues with debug or release builds? What steps are
required to reproduce them?
Note: The OsSysLog calls were just added in the last commit. No
changes were made to ares access - so I would assume that memory
corruption somewhere else is causing both aaerts.
Scott
On 1/23/09, D. S. <dsuhpublic@xxxxxxxxx> wrote:
> Building with VS 2005 and running under Windows XP.
>
> First assert
> -----------------
>
> The OsSysLog::setOutputFile(0, "sipXtapilog.txt") ; added to
> testUA.cxx causes an assert in the free(data) call in
> OsSysLogTask::handleMessage():
> case OsSysLogMsg::SET_FILE:
> data = (char*) pSysLogMsg->getData();
> processSetFile(data) ;
> if (data != NULL)
> {
> free(data) ;
> }
>
> Somehow the Windows library says that the data pointer is not a valid
> heap pointer.
>
> I would comment out all OsSysLog functions for now and uncomment the
> enableConsoleOutput(TRUE);
>
> Second assert
> ---------------------
>
> The ua.shutdown(); call in testUA.cxx causes an assert in the
> free(channel->lookups); call in ares_destroy_internal().
>
> Windows library says something similar about the heap pointer being invalid.
>
> I did not see this last week.
>
>
> I would like to find out if these problems are specific to VS 2005 or
> Windows.
>
> David Suh
> _______________________________________________
> recon-devel mailing list
> recon-devel@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/recon-devel/
>
--
Sent from my mobile device