What OS is the Processing IOC running on? If Linux, have you analyzed the core dump with gdb to see where it is crashing?
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of Poff, Mark A
Sent: Tuesday, October 07, 2014 2:56 PM
Cc: Poff, Mark A
Subject: RE: Fanout to Sub Records in a Different IOC Causes Core Dump
On the EPICS project here we’ve run into an issue which we believe
may point to a bug with fanout records and CA links - and we’re wondering if anybody else has seen this behavior. For clarity, the following simplifies our project and the records in question, but I can provide additional detail if requested.
We have two IOCs. The first IOC is responsible for publishing PVs and the second IOC is responsible for processing the PVs (using cpp routines) and placing the results in “output” PVs. The following
works with no errors:
we incorporate a fanout record (to allow two different processing routines to be called when
a single data PV changes value), the second IOC (the processing IOC)
cores almost immediately after start up:
<Identical to the first example>
As an alternate we tried placing the fanout record in the Processing IOC, but that also core’d. Has anyone seen this behavior? (I discussed this situation briefly with Andrew Johnson and he
recommended an alternate implementation using CP flags on the Processing IOC records, which works well - but of course, we’d still like to understand the issue with fanout.)