Re: [reSIProcate-users] seg fault in Connection

[Scott Godin <sgodin@xxxxxxxxxxxxxxx>]

A lot of work and testing was done on TCP transports in general after 1.5 (ie. EPOLL support).  There's a good chance whatever is causing this was fixed.  I'm not sure what this could be offhand.

Scott

On Thu, Nov 8, 2012 at 8:34 AM, Krister Jarl <kj@xxxxxxxxxxx> wrote:

Hi!

I got a segfault today. Not sure what triggered it.

(gdb) bt

#0  0x44552f00 in ?? ()

#1  0x083f3726 in resip::Connection::read (this=0x9b432e68, fifo=@0xaa460b94) at Connection.cxx:180

#2  0x082f4dcc in resip::ConnectionManager::process (this=0x867460c, fdset=@0xa1eb113c, fifo=@0xaa460b94) at ConnectionManager.cxx:266

#3  0x08414a3d in resip::TcpBaseTransport::process (this=0x8674490, fdSet=@0xa1eb113c) at TcpBaseTransport.cxx:241

#4  0x083baa35 in resip::TransportSelector::process (this=0xaa460c1c, fdset=@0xa1eb113c) at TransportSelector.cxx:266

#5  0x083a5799 in resip::TransactionController::process (this=0xaa460b8c, fdset=@0xa1eb113c) at TransactionController.cxx:85

#6  0x08397ef9 in resip::SipStack::process (this=0xaa43d008, fdset=@0xa1eb113c) at SipStack.cxx:527

We still run resiprocate 1.5, but the code doesn't seem to have changed that much compared to 1.8.

I should add that we run ConnectionManager::gc() at regular intervals to kill of old TCP-connections, but from what I can see the dtor of Connection removes the connection from the manager.

Regards,

Krister

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