Segmentation fault in FwdState::serverClosed

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Fri, 09 May 2014 01:21:07 +1200

This is a side effect of trunk rev.13388 (standby connections)

Something is still calling serverConn->close() directly instead of via
the FwdState::closeServer() method. This appears to be happening in at
least the FwdState methods connectTimeout(), dispatch() and
connectDone() error cases.

Program received signal SIGSEGV, Segmentation fault.
0x082234fa in FwdState::serverClosed (this=0x8c46488, fd=-1) at
../../src/FwdState.cc:625
625 fwdPconnPool->noteUses(fd_table[fd].pconn.uses);
(gdb) bt
#0 0x082234fa in FwdState::serverClosed (this=0x8c46488, fd=-1) at
../../src/FwdState.cc:625
#1 0x082230e6 in fwdServerClosedWrapper (params=...) at
../../src/FwdState.cc:539
#2 0x08373185 in CommCloseCbPtrFun::dial (this=0x8c3e12c) at
../../src/CommCalls.cc:211

Amos
Received on Thu May 08 2014 - 13:21:23 MDT

This archive was generated by hypermail 2.2.0 : Fri May 09 2014 - 12:00:12 MDT