Experimental Physics and Industrial Control System
|
Aloha again Allan,
Sorry, after rereading
my message, the tone sounds a bit negative
which wasn’t my intent. I should have said, “please read also the
section in the reference manual entitled - Thread
Safety and Preemptive Callback to User Code”. When designing this type of application, one must
decide if CA callbacks should occur only when periodically executing in a CA client
library function such as ca_poll, or if the CA callbacks
should occur asynchronously, as soon as the network messages are processed by
the auxiliary threads in the library. Either approach can be used in a
multi-threaded program.
Jeff
______________________________________________________
Jeffrey O. Hill
Email [email protected]
LANL MS
H820
Voice 505 665 1831
Los Alamos NM 87545 USA
FAX 505 665 5107
Message
content: TSPA
Aloha
Allan,
Ø Does the seg fault
occur because r3.13.10 is NOT thread safe?
The R3.13 CA Client library is definitely __not__ thread safe,
and I can easily imagine that this might be the cause of your seg fault.
Ø Does anyone have an
example of a multi-threaded app using r3.13.10 on UNIX?
The R3.14 CA client
library _is_ thread safe, and it should also interoperate fine with
R3.13 IOCs. We routinely operate LANSCE with that configuration in our
production system. Our control room runs R3.14, but many of our IOCs still run
R3.13. You should read the section in the reference manual entitled “Thread Safety and Preemptive Callback to User Code“.
Jeff
______________________________________________________
Jeffrey O. Hill
Email [email protected]
LANL MS
H820
Voice 505 665 1831
Los Alamos NM 87545 USA
FAX 505 665 5107
Aloha
I
am trying to get a multi-threaded application working on SunOs 5.10 with
connection to two UNIX IOC’s.
I
get a seg fault for ellDelete, two statements from the end of cac_select_io()
(epics/r3.13.10/base/src/ca/bsd_depen.c).
The
seg fault does not occur immediately but within a couple of minutes
(connections are to two IOC’s running on UNIX, with events from two long
records on each IOC, where one record on each system is updated at 1 hz and the
other at 10 hz).
Does
the seg fault occur because r3.13.10 is NOT thread safe?
Does
anyone have an example of a multi-threaded app using r3.13.10 on UNIX?
Thanks,
Allan
|
- Replies:
- RE: cac_select_io Segmentation fault Al Honey
- References:
- cac_select_io Segmentation fault Al Honey
- RE: cac_select_io Segmentation fault Jeff Hill
- Navigate by Date:
- Prev:
Re: EDM text entry: segmentation fault Eric Norum
- Next:
Re: EDM text entry: segmentation fault Dmitry Teytelman
- 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: cac_select_io Segmentation fault Jeff Hill
- Next:
RE: cac_select_io Segmentation fault Al Honey
- 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, 02 Sep 2010 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|