Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 537 of 808  Not logged in ELOG logo
    icon2.gif   Re: Elogd crashes with: *** stack smashing detected ***, posted by Stefan Ritt on Wed Jan 21 08:45:25 2009 
 

    
        
            Niklas wrote:
        
        
            
    icon2.gif   Re: Elogd crashes with: *** stack smashing detected ***, posted by Niklas on Wed Mar 4 16:32:56 2009 


    
        
            Stefan Ritt wrote:
        
        
            
             
    icon2.gif   Re: Elogd crashes with: *** stack smashing detected ***, posted by Stefan Ritt on Wed Mar 4 16:41:27 2009 

    
        
            Niklas wrote:
        
        
            

           Tried 2178 and I seem to hit some endless loop when I have big cookies. The loop seems to be in this for-loop (from gdb).
    icon2.gif   Re: Elogd crashes when submitting replies, posted by Stefan Ritt on Sat Dec 12 20:30:35 2009 


    
        
            Cliff Shaw wrote:
        
        
            
            Hi Stefan,
    icon2.gif   Re: Elogd crashes when closing more than ten entries, posted by Stefan Ritt on Fri Mar 12 13:54:14 2010 


    
        
            Cliff Shaw wrote:
        
        
            
            Hi Stefan,
    icon2.gif   Re: Elogd crashes on search, posted by Stefan Ritt on Fri Jan 31 15:27:21 2020 
Do you see the same problem on this server here?

If not, then it must be related to your specific configuration. You have to teach me how to reporduce the error in order to fix it. Best would
be a minimal elogd.cfg which causes the error.
    icon2.gif   Re: Elogd crashes on search, posted by Laurent Jean-Rigaud on Fri Jan 31 15:34:56 2020 
Hi Stefan,

The problem seems to be specific with our logbooks. Maybe one of the file is corrupted or bad string encoding ?! But how to find the source of
the problem ?
    icon2.gif   Re: Elogd crashes on search, posted by Stefan Ritt on Fri Jan 31 15:46:09 2020 
The only way for me is to reproduce it. Could be corrupted data file, or config file. Try with a new logbook with the same configuration, then add logbook
files one by one until it happens.

Stefan
ELOG V3.1.5-3fb85fa6