Argonne National Laboratory

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: Mark Rivers <rivers@cars.uchicago.edu>, "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Wed, 25 Apr 2018 05:52:15 +0000
Hello Mark

Please find the attached output from gdb when running it with the core dump.

Best Regards,
Abdalla.

-----Original Message-----
From: Abdalla Ahmad 
Sent: Wednesday, April 18, 2018 2:58 PM
To: 'Mark Rivers' <rivers@cars.uchicago.edu>; tech-talk@aps.anl.gov
Subject: RE: Problem with autosave module making it crash at random basis.

Unfortunately I deleted the core dump. Once the IOC crash again I will send the complete output. 

Abdalla.

-----Original Message-----
From: Mark Rivers [mailto:rivers@cars.uchicago.edu] 
Sent: Wednesday, April 18, 2018 2:58 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.

> The core dump is generated but GDB could not show a backtrace and reported "missing separate debuginfo for the main executable file". Is it the case that the IOC should be built with debug symbols?


I have not seen that when building with the standard non-debug EPICS_HOST_ARCH of linux-x86_64.  It will warn that some system libraries don't have debug symbols, and some variables will be shown as "optimized out", but I have always been able to get a backtrace when it crashed.


Can you send the complete output when you start gdb and try to do a backtrace?


Mark




________________________________
From: Abdalla Ahmad <abdalla.ahmad@sesame.org.jo>
Sent: Wednesday, April 18, 2018 12:46 AM
To: Mark Rivers; tech-talk@aps.anl.gov
Subject: RE: Problem with autosave module making it crash at random basis.

Hi Mark

The core dump is generated but GDB could not show a backtrace and reported "missing separate debuginfo for the main executable file". Is it the case that the IOC should be built with debug symbols?

Best Regards,
Abdalla.

-----Original Message-----
From: Mark Rivers [mailto:rivers@cars.uchicago.edu]
Sent: Sunday, April 08, 2018 4:01 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.

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: tech-talk-bounces@aps.anl.gov <tech-talk-bounces@aps.anl.gov> on behalf of Abdalla Ahmad <abdalla.ahmad@sesame.org.jo>
Sent: Sunday, April 8, 2018 1:06 AM
To: tech-talk@aps.anl.gov
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/>


GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
./bin/linux-x86/ioc iocBoot/ioc/st.cmd: No such file or directory.
Missing separate debuginfo for the main executable file
Try: yum --disablerepo='*' --enablerepo='*-debug*' install /usr/lib/debug/.build-id/29/52bbf15ac8a213b68aa5b72319418430369054
[New Thread 32361]
[New Thread 32418]
[New Thread 32424]
[New Thread 32430]
[New Thread 32436]
[New Thread 32437]
[New Thread 32438]
[New Thread 32439]
[New Thread 32440]
[New Thread 32441]
[New Thread 32442]
[New Thread 32443]
[New Thread 32447]
[New Thread 32448]
[New Thread 32449]
[New Thread 32450]
[New Thread 32451]
[New Thread 32452]
[New Thread 32453]
[New Thread 32455]
[New Thread 32456]
[New Thread 32458]
[New Thread 32460]
[New Thread 32481]
[New Thread 32482]
[New Thread 32498]
[New Thread 32499]
[New Thread 32500]
[New Thread 32501]
[New Thread 32506]
[New Thread 32507]
[New Thread 32508]
[New Thread 32509]
[New Thread 32510]
[New Thread 32511]                                                                                                                                              
[New Thread 32512]
[New Thread 32513]
[New Thread 32514]
[New Thread 32515]
[New Thread 32516]
[New Thread 32517]
[New Thread 32540]
[New Thread 32541]
[New Thread 12926]
[New Thread 12927]
[New Thread 8577]
[New Thread 8578]
[New Thread 20297]
[New Thread 26453]
[New Thread 26454]
[New Thread 32324]
[New Thread 32325]
[New Thread 32326]
[New Thread 32328]
[New Thread 32334]
[New Thread 32335]
[New Thread 32336]
[New Thread 32338]
[New Thread 32340]
[New Thread 32341]
[New Thread 32342]
[New Thread 32343]
[New Thread 32344]
[New Thread 32374]
[New Thread 24848]
[New Thread 32505]
[New Thread 32503]
[New Thread 32444]
[New Thread 32445]
[New Thread 32339]
[New Thread 32337]
[New Thread 20296]
[New Thread 24847]
[New Thread 32459]
[New Thread 32502]
[New Thread 32504]
[New Thread 32392]
[New Thread 32356]
[New Thread 32407]
[New Thread 32401]
[New Thread 32371]
[New Thread 32457]
[New Thread 32386]
[New Thread 32398]
[New Thread 32347]
[New Thread 32404]
[New Thread 32327]
[New Thread 32454]
[New Thread 32368]
[New Thread 32446]
[New Thread 32389]
[New Thread 32402]
[New Thread 32355]
[New Thread 32372]
[New Thread 32378]
[New Thread 32393]
[New Thread 32363]
[New Thread 32375]
[New Thread 32357]
[New Thread 32348]
[New Thread 32384]
[New Thread 32345]
[New Thread 32360]
[New Thread 32369]
[New Thread 32396]
[New Thread 32381]
[New Thread 32394]
[New Thread 32403]
[New Thread 32370]
[New Thread 32350]
[New Thread 32391]
[New Thread 32376]
[New Thread 32354]
[New Thread 32382]
[New Thread 32367]
[New Thread 32385]
[New Thread 32373]
[New Thread 32400]
[New Thread 32397]
[New Thread 32409]
[New Thread 32351]
[New Thread 32406]
[New Thread 32349]
[New Thread 32362]
[New Thread 32399]
[New Thread 32352]
[New Thread 32412]
[New Thread 32365]
[New Thread 32411]
[New Thread 32358]
[New Thread 32346]
[New Thread 32377]
[New Thread 32408]
[New Thread 32366]
[New Thread 32353]
[New Thread 32395]
[New Thread 32364]
[New Thread 32383]
[New Thread 32380]
[New Thread 32387]
[New Thread 32379]
[New Thread 32359]
[New Thread 32405]
[New Thread 32410]
[New Thread 32388]
[New Thread 32390]
Core was generated by `./bin/linux-x86/ioc iocBoot/ioc/st.cmd'.
Program terminated with signal 11, Segmentation fault.
#0  0x00399969 in ?? ()
(gdb) backtrace
#0  0x00399969 in ?? ()
#1  0x08d928c0 in ?? ()
#2  0x00a697fa in ?? ()
#3  0x08dd2510 in ?? ()
#4  0x00307a49 in ?? ()
#5  0x08d92cf0 in ?? ()
#6  0x00640aae in ?? ()
(gdb) 

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
RE: 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: Walking Piezo Drivers/ Controllers Survey Wallace, Alex
Next: Modify checkbox value from a table widget Pilar Gil Jaldo
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. Abdalla Ahmad
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  <20182019 
ANJ, 25 Apr 2018 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·