Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG  Not logged in

Back  |  Find  |  Login  |  Help

Creating logbook by copying an existing one crashes elog, posted by Chris Howe on Thu Jul 28 15:33:21 2005        Re: Creating logbook by copying an existing one crashes elog, posted by Stefan Ritt on Thu Aug 4 21:36:21 2005

Message ID: 1358     Entry time: Thu Jul 28 15:33:21 2005     Reply to this: 1372 Icon:   Author: Chris Howe  Author Email: c.j.howe@rl.ac.uk  Category: Bug report  OS: Windows  ELOG Version: 2.6.0  Subject: Creating logbook by copying an existing one crashes elog

Hi, Trying to create a new logbook from an existing one causes elog to crash. output from DrMingw: elogd.exe caused an Access Violation at location 00448c6e in module elogd.exe Writing to location 6e206c65. Registers: eax=00240798 ebx=00000020 ecx=6e206c61 edx=00250088 esi=00000000 edi=69726500 eip=00448c6e esp=01c1a1d0 ebp=01c1a1f0 iopl=0 nv up ei ng nz ac po cy cs=001b ss=0023 ds=0023 es=0023 fs=0038 gs=0000 efl=00000297 Call stack: 00448C6E elogd.exe:00448C6E 00445F17 elogd.exe:00445F17 as the service restarts elog the browser then displays: "Cannot open file elog.pwd: No such file or directory Please use your browser's back button to go back" If you try and create a new logbook from scratch (i.e. not a copy) then the browser displays: "Cannot open file elog.pwd: No such file or directory Please use your browser's back button to go back" In both cases the new logbook is created. any ideas? Chris

ELOG V3.1.5-fe60aaf