Hi Jeff,
On Thursday 21 April 2011 17:54:11 Jeff Hill wrote:
> > However unless you use the epicsThread routines in libCom
> > to create that thread I don't believe it will have any way
> > to clean up the context again when that thread exits
>
> The R3.14 ca library, will implicitly create a ca context for the thread
> that does not call ca_create_context before it uses ca functions, but in
> fact it will not implicitly destroy that context when the thread exits.
Ah, I thought you might be registering an epicsAtThreadExit() handler and keep
a reference count on the number of threads using each context, but on
reflection I see that would be a rather brittle approach since an application
could be managing its own contexts privately without you knowing about it.
Thanks for the clarification,
- Andrew
--
An error is only a mistake if you don't learn from it.
When you learn something from it, it becomes a lesson.
- References:
- PyEpics and Python threads Vigder, Mark
- Re: PyEpics and Python threads Andrew Johnson
- RE: PyEpics and Python threads Jeff Hill
- Navigate by Date:
- Prev:
Re: #RE: About ASG usage jun-ichi.odagiri
- Next:
VMIC VMIVME 4105 register cannot be modified? 马晓媛
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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:
RE: PyEpics and Python threads Jeff Hill
- Next:
EPICS Base v3.14.12.1-rc1 compilation error Ritesh Sugandhi
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
<2011>
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|