Experimental Physics and Industrial Control System
Hi Jeff,
Jeff Hill wrote:
I committed to CVS this evening an upgrade to epicsExit (see epicsExit.h)
allowing a thread (thread private) exit handler to be installed. This is
Looks good, the test passes on Solaris; I will check vxWorks and report
any problems when I next run the libCom test suite there.
I am calling the exit handlers directly from the thread entry wrapper. That
approach might not work correctly if the thread exits indirectly. For
example via the exit() call. There might be OS dependent solutions for that
weakness.
I added the following descriptions to the Application Developers Guide:
*epicsExitCallAtThreadExits*
This calls each of the functions registered by the calling thread having
called epicsAtThreadExit. This is done automatically when an
epicsThread's main entry method returns, and will not be done if the
thread is stopped by other means.
*epicsAtThreadExit*
Register a function to be called when epicsExitCallAtThreadExits is
invoked by the current thread.
- Andrew
--
There is considerable overlap between the intelligence of the smartest
bears and the dumbest tourists -- Yosemite National Park Ranger
- Replies:
- RE: thread private exit hook added to EPICS base for R3.14.9 Jeff Hill
- References:
- thread private exit hook added to EPICS base for R3.14.9 Jeff Hill
- Navigate by Date:
- Prev:
thread private exit hook added to EPICS base for R3.14.9 Jeff Hill
- Next:
RE: thread private exit hook added to EPICS base for R3.14.9 Jeff Hill
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
thread private exit hook added to EPICS base for R3.14.9 Jeff Hill
- Next:
RE: thread private exit hook added to EPICS base for R3.14.9 Jeff Hill
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024