pjsip_inv_send_msg segfault fix

AG
Alexei Gradinari
Thu, May 11, 2017 9:15 PM

Segmentation fault.
#0  0x00007fd9306aa015 in pjsip_inv_send_msg (inv=0x7fd90835c2a8, tdata=tdata@entry=0x7fd935a8cc28)
at pjsip/src/pjsip-ua/sip_inv.c:3219
cseq = 0x7fd935a8d6f8
status = <optimized out>

Attached a patch which locks inv->dlg to use inv->invite_tsx->cseq

Regards,
Alexei

Segmentation fault. #0 0x00007fd9306aa015 in pjsip_inv_send_msg (inv=0x7fd90835c2a8, tdata=tdata@entry=0x7fd935a8cc28) at pjsip/src/pjsip-ua/sip_inv.c:3219 cseq = 0x7fd935a8d6f8 status = <optimized out> Attached a patch which locks inv->dlg to use inv->invite_tsx->cseq Regards, Alexei
AG
Alexei Gradinari
Thu, May 11, 2017 10:17 PM

Segmentation fault.
#0  0x00007fd9306aa015 in pjsip_inv_send_msg (inv=0x7fd90835c2a8, tdata=tdata@entry=0x7fd935a8cc28)
at pjsip/src/pjsip-ua/sip_inv.c:3219
cseq = 0x7fd935a8d6f8
status = <optimized out>

Attached the revised patch

Regards,
Alexei

> Segmentation fault. > #0 0x00007fd9306aa015 in pjsip_inv_send_msg (inv=0x7fd90835c2a8, tdata=tdata@entry=0x7fd935a8cc28) > at pjsip/src/pjsip-ua/sip_inv.c:3219 > cseq = 0x7fd935a8d6f8 > status = <optimized out> Attached the revised patch Regards, Alexei
NI
Nanang Izzuddin
Tue, May 16, 2017 5:37 AM

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@gmail.com
wrote:

Segmentation fault.
#0  0x00007fd9306aa015 in pjsip_inv_send_msg (inv=0x7fd90835c2a8,

tdata=tdata@entry=0x7fd935a8cc28)

 at pjsip/src/pjsip-ua/sip_inv.c:3219
     cseq = 0x7fd935a8d6f8
     status = <optimized out>

Attached the revised patch

Regards,
Alexei


Visit our blog: http://blog.pjsip.org

pjsip mailing list
pjsip@lists.pjsip.org
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

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@gmail.com> wrote: > > Segmentation fault. > > #0 0x00007fd9306aa015 in pjsip_inv_send_msg (inv=0x7fd90835c2a8, > tdata=tdata@entry=0x7fd935a8cc28) > > at pjsip/src/pjsip-ua/sip_inv.c:3219 > > cseq = 0x7fd935a8d6f8 > > status = <optimized out> > > Attached the revised patch > > Regards, > Alexei > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip@lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > >