EPICS Home

Experimental Physics and Industrial Control System


 
1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  <20182019  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  <20182019 
<== Date ==> <== Thread ==>

Subject: RE: Problem with autosave module making it crash at random basis.
From: "Abdalla Ahmad" <abdalla.ahmad@sesame.org.jo>
To: Michael Davidsaver <mdavidsaver@gmail.com>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Wed, 18 Apr 2018 05:49:41 +0000
Hi Michael

Since the OS is Scientific Linux 6.4 and will be upgraded to CentOS, I went for the newest version of the autosave module for now because I could not find the RPM in the local repo.

The build process did not report any warning, so the newest version is.

Best Regards,
Abdalla.

-----Original Message-----
From: Michael Davidsaver [mailto:mdavidsaver@gmail.com] 
Sent: Monday, April 09, 2018 7:16 PM
To: Abdalla Ahmad <abdalla.ahmad@sesame.org.jo>; tech-talk@aps.anl.gov
Subject: Re: Problem with autosave module making it crash at random basis.

A couple of points

* save_restore.c includes epicsStdio.h so it is using IOC shell redirection.
So the FILE* being used is not directly stdout/stderr.

* Installing debug symbol RPM for libc.so might give some more information about whether the error involves the FILE*, the string buffer, or one of the arguments to be formatted.

* Look for printf() format related warnings from GCC when building autosave.
It's not unheard of for incorrect format specs in (rarely run) error path prints to turn a recoverable error into a crash.


On 04/07/2018 11:06 PM, Abdalla  Ahmad wrote:
> 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/>
> 
>  
> 


References:
Problem with autosave module making it crash at random basis. Abdalla Ahmad
Re: Problem with autosave module making it crash at random basis. Michael Davidsaver

Navigate by Date:
Prev: RE: Problem with autosave module making it crash at random basis. Abdalla Ahmad
Next: Re: areaDetector question Jörn Dreyer
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  <20182019 
Navigate by Thread:
Prev: Re: Problem with autosave module making it crash at random basis. Michael Davidsaver
Next: Re: Problem with autosave module making it crash at random basis. Konrad, Martin
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  <20182019