Experimental Physics and Industrial Control System
|
To be honest, I dont know if it's safe for a signal handler to join a
thread context. There's at least one possible race condition in this
case: the signal handler could execute after ca_task_exit() has been
called. What other race conditions are you thinking about?
I'm sure Jeff will weigh in when he gets back.
Chris Timossi
Eric Norum wrote:
Robert Soliday wrote:
Thanks, this solved my problem.
--Bob
Chris Timossi wrote:
Robert,
I believe that you should replace ca_task_initialize with
> ca_context_create(ca_enable_preemptive_callback) in main. Then in the
> interrupt handler, you can call ca_current_context() to get the
> current context and finally join that context with
> ca_attach_context().
Are you sure that this is safe? I suspect that calling these
functions from a signal handler is going to introduce all sorts of
race conditions.
Jeff -- can you confirm/deny my suspicions?
- Replies:
- Re: Proglem doing CA calls after catching a signal Eric Norum
- References:
- Proglem doing CA calls after catching a signal Robert Soliday
- Re: Proglem doing CA calls after catching a signal Robert Soliday
- Re: Proglem doing CA calls after catching a signal Eric Norum
- Navigate by Date:
- Prev:
Re: Proglem doing CA calls after catching a signal Eric Norum
- Next:
CGI Export wtw00992
- 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: Proglem doing CA calls after catching a signal Eric Norum
- Next:
Re: Proglem doing CA calls after catching a signal Eric Norum
- 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
|
ANJ, 10 Aug 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|