Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon5.gif   deadc0de, posted by Niklas on Fri Aug 1 13:47:58 2008 
    icon2.gif   Re: deadc0de, posted by Stefan Ritt on Mon Aug 4 09:00:43 2008 
       icon2.gif   Re: deadc0de, posted by Niklas on Thu Nov 13 19:27:02 2008 
          icon2.gif   Re: deadc0de, posted by Niklas on Fri Nov 14 08:48:05 2008 
             icon2.gif   Re: deadc0de, posted by Eoin Butler on Thu Dec 18 10:32:09 2008 
                icon2.gif   Re: deadc0de, posted by Stefan Ritt on Thu Dec 18 10:39:57 2008 
                   icon2.gif   Re: deadc0de, posted by Eoin Butler on Thu Dec 18 11:16:37 2008 
                      icon2.gif   Re: deadc0de, posted by Stefan Ritt on Thu Dec 18 11:51:07 2008 
Message ID: 65942     Entry time: Mon Aug 4 09:00:43 2008     In reply to: 65941     Reply to this: 66045
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS: Linux  ELOG Version: 2.7.3 
Subject: Re: deadc0de 

Niklas wrote:

my ELOG sometimes dies with "deadc0de", do I have too large ELOG config or logbook? Or is it simply a bug?

What can I do to solve this problem? "ulimit"? Or some trace output from elog?

 This seems an internal memory allocation problem. Can you reproduce the error? Can you reproduce it with the minimal configuration file coming with the distribution? If you know how to run a program inside the debugger, you can send me a stack trace when the problem occurs and I can check it.

ELOG V3.1.5-fe60aaf