EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: RE: thread private exit hook added to EPICS base for R3.14.9
From: "Jeff Hill" <[email protected]>
To: "'Andrew Johnson'" <[email protected]>
Cc: "'EPICS Core Talk'" <[email protected]>, "'Ernest L. Williams Jr.'" <[email protected]>, "'John D. Galambos'" <[email protected]>, "'Matej Sekoranja'" <[email protected]>, "'Tom Pelaia II'" <[email protected]>
Date: Thu, 7 Dec 2006 09:53:48 -0700
*epicsAtThreadExit*

This registers a callback function to be called when
epicsExitCallAtThreadExits is invoked by the current thread. A void pointer
context parameter is also supplied when registering the function. This
context parameter is supplied as the sole argument to the callback function
when it is invoked.

*epicsExitCallAtThreadExits*

This calls each of the thread termination callback functions registered by
the calling thread when it called epicsAtThreadExit. This is done
automatically when the function specified to epicsThreadCreate returns, and
will not be done if thread execution is terminated by other means.

> -----Original Message-----
> From: Andrew Johnson [mailto:[email protected]]
> Sent: Thursday, December 07, 2006 8:55 AM
> To: Jeff Hill
> Cc: 'EPICS Core Talk'; Ernest L. Williams Jr.; 'John D. Galambos'; 'Matej
> Sekoranja'; 'Tom Pelaia II'
> Subject: Re: thread private exit hook added to EPICS base for R3.14.9
> 
> 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


References:
Re: thread private exit hook added to EPICS base for R3.14.9 Andrew Johnson

Navigate by Date:
Prev: Re: thread private exit hook added to EPICS base for R3.14.9 Andrew Johnson
Next: RE: Ca portable server Enum strin table Jeff Hill
Index: 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: thread private exit hook added to EPICS base for R3.14.9 Andrew Johnson
Next: RE: Ca portable server Enum strin table Jeff Hill
Index: 2002  2003  2004  2005  <20062007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 02 Feb 2012 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·