Experimental Physics and Industrial Control System
|
I am opposed to the addition of epicsThreadDelete(). We looked long
and hard at that capability when creating the OSI libraries and
decided to leave it out. At the very least there is almost a
guarantee of resource leakage when killing a thread from the
outside. There's also the possibility of leaving a lock somewhere
or an open file left dangling. I would say that the only thing safe
to do after killing another thread would be to reboot the IOC
(vxWorks, RTEMS) or terminate the process (posix, etc.) -- and if
you're going to do that you may as well just avoid the thread delete
in the first place!
--
Eric Norum <[email protected]>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793
- Replies:
- epicsThreadDelete Re: Redundancy Patches Kay-Uwe Kasemir
- References:
- Redundancy Patches Andrew Johnson
- Navigate by Date:
- Prev:
Redundancy Patch: makeBaseApp Andrew Johnson
- Next:
epicsThreadDelete Re: Redundancy Patches Kay-Uwe Kasemir
- 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:
Redundancy Patches Andrew Johnson
- Next:
epicsThreadDelete Re: Redundancy Patches Kay-Uwe Kasemir
- Index:
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|
ANJ, 02 Feb 2012 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|