Hi Alexei,
Looks like it is related to an access to an already nulled inv->invite_tsx. Unfortunately we cannot be so sure whether this is a library bug, so for investigation could you also send a complete call stack trace and PJSIP log file or reproducing steps of the segmentation fault scenario? Thank you.
BR,
nanang
On Fri, May 12, 2017 at 5:17 AM, Alexei Gradinari <alex2grad@xxxxxxxxx> wrote:
> Segmentation fault.
> #0 0x00007fd9306aa015 in pjsip_inv_send_msg (inv=0x7fd90835c2a8, tdata=tdata@entry=0x7fd935a8cc28) Attached the revised patch
> at pjsip/src/pjsip-ua/sip_inv.c:3219
> cseq = 0x7fd935a8d6f8
> status = <optimized out>
Regards,
Alexei
_______________________________________________
Visit our blog: http://blog.pjsip.org
pjsip mailing list
pjsip@xxxxxxxxxxxxxxx
http://lists.pjsip.org/mailman/listinfo/pjsip_lists. pjsip.org
_______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip@xxxxxxxxxxxxxxx http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
