The IOC crashed but no core dump was found. The server is Scientific Linux 6.4, I did some search and I found out I have to enable core dumps through /etc/security/limits and /etc/sysct.conf , see here for example [ https://www.unixmen.com/how-to-enable-core-dumps-in-rhel6 ]. I did those and waiting for the IOC to crash.
From: Mark Rivers [mailto:firstname.lastname@example.org]
Sent: Sunday, April 08, 2018 4:01 PM
To: Abdalla Ahmad <email@example.com>; firstname.lastname@example.org
Subject: Re: Problem with autosave module making it crash at random basis.
The latest autosave Makefile contains these lines:
# To enable autosaveBuild, use dbLoadRecordsHookRegister(). (Requires EPICS # base 184.108.40.206 or later.) USR_CFLAGS += -DDBLOADRECORDSHOOKREGISTER
Since you are running 220.127.116.11 I think you should try commenting out that USR_CFLAGS line.
With your older version of autosave your output showed that valgrind itself had crashed. You should be able to get a traceback without valgrind, just by enabling core dumps. Type the following commands:
On bash shell:
ulimit -c 10000000
or on csh shell:
limit core 1000000
Then run the IOC application. When it crashes it will create a core.xxxxxx file.
Then run the Gnu debugger:
gdb path/to/your/IOC/executable core.xxxxxx
You need to provide the path to your IOC executable and replace core.xxxxxx with the name of the core file it just created.
Once you are in the debugger type:
It will show a stack dump to where it crashed.
From: email@example.com <firstname.lastname@example.org> on behalf of Abdalla Ahmad <email@example.com>
Sent: Sunday, April 8, 2018 1:06 AM
Subject: Problem with autosave module making it crash at random basis.
One of our IOCs crashed and it appears to do so from time to time. I used valgrind on the IOC process and the attached file contains valgrind output right when the IOC crashed. The first 2 lines are the IOC shell output before the segmentation fault happened. I could not figure out whether the problem from the module sending something corrupted to the printf functions or the standard C library itself is somehow corrupted. I tried cloning the latest autosave version from github but the build failed. Build output is in the attached too.
OS: Scientific Linux 6.4 32-bit.
Tel: (+962-5) 3511348 , ext. 265
Fax: (+962-5) 3511423
- Problem with autosave module making it crash at random basis. Abdalla Ahmad
- Re: Problem with autosave module making it crash at random basis. Mark Rivers
- Navigate by Date:
Re: EPICS 7 Compilation in windows-64 Mark Rivers
Re: EPICS 7 Compilation in windows-64 Vishnu Patel
- Navigate by Thread:
Re: Problem with autosave module making it crash at random basis. Mark Rivers
RE: Problem with autosave module making it crash at random basis. Abdalla Ahmad