Re: [reSIProcate] Crash in ares on deleting SipStack
I did a little digging, and saw some people running into issues where strdup() was using a different version of the malloc library than free() did (due to link errors). Does this sound like something you might be encountering here? If strdup is using different malloc code than the free called later, this would explain your heap-corruption.
Best regards, Byron Campen We’re experiencing a heap corruption / crash in Ares when deleting the SipStack object running on Windows XP and compiled with Visual Studio 2003. In ares_destroy.c, ares_destroy_internal, around line 45 … free(channel->lookups) … causes a heap corruption report in the debugger. Changing the strdup to _strdup in ares_init.c where “bf” or the supplied string are duplicated into ->lookups resolves the problem. Has anyone else experienced this problem? Thanks,
Steve Coule
Envox UK Ltd _______________________________________________ resiprocate-devel mailing list
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature