EPICS Base R3.15.3: Known Problems
Any patch files linked below should be applied at the root of the
base-3.15.3 tree. Download them, then use the GNU Patch program as
follows:
% cd /path/to/base-3.15.3
% patch -p0 < /path/to/file.patch
The following significant problems have been reported with this
version of EPICS Base:
- 2016-03-30: Initializing a string record with a string longer than 40
characters can cause the IOC to crash at iocInit (see Launchpad
bug 1563191).
This patch prevents both bugs.
- 2016-03-30: The C++ version of the epicsThread API can corrupt memory
in some circumstances when the thread exits (see Launchpad
bug 1558206).
This patch fixes the problem.
- 2016-01-07: C++ users of the epicsMMIO.h code under VxWorks must apply
this patch to prevent the names of several
routines from being mangled incorrectly. This particularly applies to users
of the mrfioc2 support module.
- 2015-11-24: A patch to fix the Launchpad bug
#1466129
is available here. This
patch must be applied if any non-Windows IOCs need the recently-added
feature that allows an IOC to bind to a single network interface using the
EPICS_CAS_INTF_ADDR_LIST environment variable. This patch has only been
tested on 64-bit Linux systems but may work on other targets; a complete fix
is expected to be included in the 3.15.4 release.
- Parallel builds ("make -j") on native Windows may not work properly. Such
builds can hang, saturating one core; interrupting and running make again
usually finishes the build. Limiting the number of jobs running in parallel
using something like "make -j8" (where 8 is the number of CPUs your system
has) also helps to prevent this problem. Sequential builds always work and
are recommended for automated build environments.
- 64-bit Windows builds of the CAS library may not work with some compilers.
The code in src/legacy/gdd is currently incompatible with the LLP64
model that Windows uses for its 64-bit ABI.