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