Experimental Physics and Industrial Control System
|
Chris Larrieu wrote:
Isn't the crux of the problem that there's no way to specify/predict
which thread should handle a signal?
Assuming that signal disposition is a per-thread attribute (big assumption 1)
and assuming that signal disposition really works on all platforms (big
assumption 2) we could ensure that the main (startup) thread got the signal if
we had epicsThreadCreate call sigprocmask to block signals in all created
(i.e. non-main) threads. Of course dealing with signals that arrived right
during the thread creation would probably still be an issue.
My recommendation to Bob Soliday remains, "try to find a way to deal with this
situtation that doesn't involve catching signals".
--
Eric Norum [email protected]
Advanced Photon Source Phone: (630) 252-4793
Argonne National Laboratory
- References:
- Proglem doing CA calls after catching a signal Robert Soliday
- Re: Proglem doing CA calls after catching a signal Eric Norum
- Re: Proglem doing CA calls after catching a signal Till Straumann
- Re: Proglem doing CA calls after catching a signal Chris Larrieu
- Navigate by Date:
- Prev:
Re: Proglem doing CA calls after catching a signal Chris Larrieu
- Next:
Re: Proglem doing CA calls after catching a signal Robert Soliday
- 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 Chris Larrieu
- Next:
Re: Proglem doing CA calls after catching a signal Robert Soliday
- 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
·
|