Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Crash report involving propagate and replies, posted by Stephen on Tue Nov 26 16:24:39 2013 elogd.cfg
    icon2.gif   Re: Crash report involving propagate and replies, posted by David Pilgram on Tue Nov 26 21:49:42 2013 
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Wed Nov 27 15:22:37 2013 
    icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Dec 2 09:27:35 2013 elogd.cfg
    icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Dec 2 09:58:42 2013 elogd.cfgelog.png
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Mon Dec 2 23:02:45 2013 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Tue Dec 3 11:30:43 2013 
             icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Fri Jan 3 21:33:40 2014 error1.jpgerror2.jpgerror3.jpg
                icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 6 10:25:03 2014 
                icon2.gif   Re: Crash report involving propagate and replies, posted by Andreas Luedeke on Mon Jan 6 10:32:43 2014 
                   icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Sun Jan 12 04:48:12 2014 test.jpgtest2.jpg
                      icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 13 09:01:31 2014 
    icon2.gif   Re: Crash report involving propagate and replies, posted by Stefan Ritt on Mon Jan 13 09:30:09 2014 
       icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Fri Jan 24 18:59:17 2014 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Stephen on Wed Jan 29 17:13:55 2014 
          icon2.gif   Re: Crash report involving propagate and replies, posted by Hung Dao on Mon Feb 3 22:45:10 2014 
Message ID: 67648     Entry time: Mon Jan 13 09:01:31 2014     In reply to: 67647
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Bug report  OS: Windows  ELOG Version: 2.9.2 
Subject: Re: Crash report involving propagate and replies 

 I don't see it has crashed when testing your cfg.  However, one thing I must do is to comment out the alarm_handler function in order to compile the elogd successfully.  Otherwise, it shows an undefined alarm, see in the 2nd attachment.  Although it did not crash as tested with your cfg, I have experienced the new version sometimes crashed on our system but then it self restarted (different scenario since my cfg does not use Propagate.  I have not been able to narrow down yet.

Yes, the alarm() function is wrong here. I removed it from the Windows version and committed the code to GIT. 

ELOG V3.1.5-fe60aaf