The client libs receive thread last chance except handler should cause abort shutdown

[Jeff Hill]

I am looking at line 594 in tcpiiu.cpp and wondering if initiateAbortShutdown should be called when an unexpected exception arrives.

Original Mantis Bug: mantis-366
    http://www.aps.anl.gov/epics/mantis/view_bug_page.php?f_id=366

[Jeff Hill (johill-lanl)]

committed a fix

cvs diff -wb -- tcpiiu.cpp (in directory C:\hill\epics\base\src\ca\)
Index: tcpiiu.cpp
===================================================================
RCS file: /net/phoebus/epicsmgr/cvsroot/epics/base/src/ca/tcpiiu.cpp,v
retrieving revision 1.154.2.48
diff -u -b -w -b -r1.154.2.48 tcpiiu.cpp
--- tcpiiu.cpp 14 Aug 2009 17:31:34 -0000 1.154.2.48
+++ tcpiiu.cpp 11 Sep 2009 00:44:25 -0000
@@ -582,17 +582,23 @@
             "CA client library tcp receive thread "
             "terminating due to no space in pool "
             "C++ exception\n" );
+ epicsGuard < epicsMutex > guard ( this->iiu.mutex );
+ this->iiu.initiateCleanShutdown ( guard );
     }
     catch ( std::exception & except ) {
         errlogPrintf (
             "CA client library tcp receive thread "
             "terminating due to C++ exception "%s"\n",
             except.what () );
+ epicsGuard < epicsMutex > guard ( this->iiu.mutex );
+ this->iiu.initiateCleanShutdown ( guard );
     }
     catch ( ... ) {
         errlogPrintf (
             "CA client library tcp receive thread "
- "terminating due to a C++ exception\n" );
+ "terminating due to a non-standard C++ exception\n" );
+ epicsGuard < epicsMutex > guard ( this->iiu.mutex );
+ this->iiu.initiateCleanShutdown ( guard );
     }
 }

[Jeff Hill (johill-lanl)]

seems to work after some limited testing throwing an artificial exception

[mdavidsaver (mdavidsaver)]

Looks like this change was in 3.14.11.