Experimental Physics and
Industrial Control System

"Ronald L. Sluiter" <[email protected]> · Mon, 22 Jan 2018 11:10:43 -0600

As an alternative to the using the core dump, you could rebuild your system and

the IOC using the

"linux-x86_64-debug" EPICS_HOST_ARCH. After that you have to test the IOC to see

if the same

caserverio.c line #357 assert() error occurs under the non-optimized

"linux-x86_64-debug" architecture.

If you can re-create the problem using the "linux-x86_64-debug" architecture,

then you can use a

source-code debugger (e.g., gdb or ddd) to diagnose it. You would need to place

an assembly-code

level breakpoint in the assert() code to determine why the assert() failed.

Ron

On 01/19/2018 10:35 AM, Hinko Kocevar wrote:

Thanks again!

I can see that if I run a faulty app that would trigger core dump the
file is saved into /var/spool/abrt folder.

I can not see IOC core dump there.. Might be due to redhat/centos abrt
service default settings that only saves core dump if the package was
installed using yum or similar. My IOC was not. This, I changed now,
but that means I need to reproduce the crash. Will update you on the
progress.

/Hinko

On Fri, Jan 19, 2018 at 4:17 PM, Michael Davidsaver
<[email protected]> wrote:

On 01/19/2018 12:31 AM, Hinko Kocevar wrote:

if core saving was
enabled at the time of the crash..

Run

ulimit -a

and look for a line like:

core file size          (blocks, -c) 0

If this is zero, then core dumps are disabled.  Run

ulimit -c unlimited

To enable core dumps.  You can use a non-zero
value to limit the core file size, but that's
probably not relevant unless your IOC is using
a _lot_ of memory.

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System