[reSIProcate] issue about stack crash when sip messageparsing on MAC OS
Dmytro Bogovych
dmytro.bogovych at gmail.com
Sun May 24 02:06:35 CDT 2020
Clang's AddressSanitizer is memory checking option. Useful to fix hard looking problems.
On May 23 2020, at 4:14 pm, lvbin <lvbin at xylink.com> wrote:
> Thank you for your answer!
>
> I am using the latest version of resiprocate v1.12.0. I just copied the code of “BasicCall.cxx” in resip/dum/test/ into my project. I created UAC and UAS object, then ran the code. By Wireshark, I can catch the signaling OPTION and INVITE sent by UAC, but when UAS received them the stack crashed. So I don’t think it was caused by clang's AddressSanitizer and callbacks.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20200524/aed7f1cd/attachment.htm>
More information about the resiprocate-devel
mailing list