Re: [reSIProcate-users] TransactionState assert, sendCurrentToWire

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

Hi Krister,

It seems that mNextTransmission is being cleared out prematurely somehow.  Do you have a stack level log of this?

Scott

On Tue, Nov 20, 2012 at 4:34 AM, Krister Jarl <kj@xxxxxxxxxxx> wrote:

Hi,

we recently upgraded to 1.8.5 from 1.5, but we've found a rare issue where TransactionState fails in sendCurrentToWire. Our application logs show no hint on what has happened. Looking the TransactionState object in frame 3 it seems to be a CANCEL. I've applied the patch for the CANCEL issue reported earlier (http://list.resiprocate.org/archive/resiprocate-devel/msg08100.html)

#0  0x00007f6a2a99ded5 in raise () from /lib/libc.so.6
#1  0x00007f6a2a99f3f3 in abort () from /lib/libc.so.6
#2  0x00007f6a2a996dc9 in __assert_fail () from /lib/libc.so.6
#3  0x0000000000766e2f in resip::TransactionState::sendCurrentToWire (this=0x7f6a1fe40800) at TransactionState.cxx:2579
#4  0x000000000076840c in resip::TransactionState::processServerNonInvite (this=0x7f6a1fe40800, msg=0x7f6a1fa8acf0)
    at TransactionState.cxx:1461
#5  0x000000000076e388 in resip::TransactionState::process (controller=@0x7f6a1e309f70, message=0x7f6a1fa8acf0)
    at TransactionState.cxx:719
#6  0x000000000075fe8d in resip::TransactionController::process (this=0x7f6a1e309f70, timeout=-1)
    at TransactionController.cxx:141
#7  0x0000000000753c74 in resip::SipStack::processTimers (this=0x7f6a1e30db00) at SipStack.cxx:790

Regards,
Krister

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/