Hi Mark
That was really helpful. Thank you very much. The latest autosave has been built but I kept the IOC loaded against the current version and performed your debugging instructions. I will reply once the IOC crashes.
One question, I forgot to mention that we are running the IOC inside a TMUX session, will this make a difference on the debugging part?
Best Regards,
Abdalla.
-----Original Message-----
From: Mark Rivers [mailto:[email protected]]
Sent: Sunday, April 08, 2018 4:01 PM
To: Abdalla Ahmad <[email protected]>; [email protected]
Subject: Re: Problem with autosave module making it crash at random basis.
Hi Abdalla,
The latest autosave Makefile contains these lines:
# To enable autosaveBuild, use dbLoadRecordsHookRegister(). (Requires EPICS # base 3.14.12.5 or later.) USR_CFLAGS += -DDBLOADRECORDSHOOKREGISTER
Since you are running 3.14.12.3 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:
backtrace
It will show a stack dump to where it crashed.
Mark
________________________________
From: [email protected] <[email protected]> on behalf of Abdalla Ahmad <[email protected]>
Sent: Sunday, April 8, 2018 1:06 AM
To: [email protected]
Subject: Problem with autosave module making it crash at random basis.
Hi
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.
EPICS: 3.14.12.3
SynApps 5.6
Autosave 4.8
Best Regards,
Abdalla Ahmad
Control Engineer
SESAME
Allan, Jordan.
Tel: (+962-5) 3511348 , ext. 265
Fax: (+962-5) 3511423
Mob: (+962-7)88183296
www.sesame.org.jo<http://www.sesame.org.jo/>
- Replies:
- Re: Problem with autosave module making it crash at random basis. Mark Rivers
- References:
- 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:
- Prev:
Re: Problem with autosave module making it crash at random basis. Mark Rivers
- Next:
RE: question about pvAccess monitor [email protected]
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Problem with autosave module making it crash at random basis. Mark Rivers
- Next:
Re: Problem with autosave module making it crash at random basis. Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
<2018>
2019
2020
2021
2022
2023
2024
|