Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon13.gif   E-log crash, posted by soren poulsen on Thu May 14 17:41:44 2009 
    icon2.gif   Re: E-log crash, posted by Stefan Ritt on Thu May 14 17:59:04 2009 
       icon2.gif   Re: E-log crash, posted by soren poulsen on Tue May 19 15:19:16 2009 
    icon2.gif   Re: E-log crash, posted by Stefan Ritt on Thu Jun 4 14:05:58 2009 
Message ID: 66364     Entry time: Tue May 19 15:19:16 2009     In reply to: 66362
Icon: Reply  Author: soren poulsen  Author Email: soren.poulsen@cern.ch 
Category: Bug report  OS: Linux  ELOG Version: 2.7.6 
Subject: Re: E-log crash 

Stefan Ritt wrote:

 

soren poulsen wrote:

Hi

I am having a little problem with e-log that I can easily reproduce.

I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.

So this only happens when I am not observing the input formats or the mandatory fields.

This is the GDB trace. This is not very verbose, so I must learn to use the other tracers, I guess.

Server listening on port 8079 ...
 
Program received signal SIGSEGV, Segmentation fault.
0x0000000000414077 in is_script (
    s=0x7fff1a0b89a0 "<a href=\"https://edh.cern.ch/Document/DAI/\"\"></a>")
    at src/elogd.c:5414
5414       for (i = 0; script_tags[i][0]; i++) {
(gdb)

Soren

 

It would be best if I could reproduce your problem. So can you start from a very simple configuration file, add your constraints until the problme happens, and then send me the config file? 

Hi

The problem is not exactly what I thought, but I did track it down. Here is a logbook definition that reliably creates a segmentation fault in e-log. This logbook's only useful purpose is in fact to create a segmentation fault:

You select "New", then "Select", without entering anything.

--------------

Login user = Admin

Attributes = Link

Change Link = <a href="https://$Link"">$Link</a>

---------------

I would be able to create some more debugging information of course, if needed.
 

Regards

Soren

 

ELOG V3.1.5-3fb85fa6