Re: Elog ID entry bug at >99999 entries, posted by Joseph McKenna on Tue May 8 16:17:28 2018
|
Thank you all for your kind responses. Please consider this thread resolved: no bug in elog
Chris
Rasmussen wrote:
ah yes, that was a helpful clue. Our elogd.cfg file led me to a |
elogd service crashes after windows update, posted by Tom Roberts on Fri May 18 00:57:33 2018
|
We have been using elog on Windows 10 for a long time. Today, after a Windows update, the elogd service started crashing (error 1067, unexpected termination).
It ran fine just before the Windows update (which took > 1 hour, so it was a major one). Uninstalling and re-installing did not help, including replacing
my elogd.cfg with the default. Installing on another PC (that also has this update) fails in the same way. I have a good backup of my logbook. |
|
Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Tue Sep 11 19:46:40 2018
|
Tried compiling on FC27 and 28, both result in binaries but with serious issues; writing data larger than then allowed.
Example output:
make
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations |
Re: Compile issues on Fedora withe current elog source, posted by Stefan Ritt on Wed Sep 12 11:10:18 2018
|
This warning is triggered by the use of the sprintf() funciton, which can write beyond the boundary of the destination string. I replaced it by snprintf(),
which should make the compiler happy. Code is committed. Unfortuantely I have no FC27 here, so if there is still some waring with the current code, please
post the full warning list here. |
|
Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:20:11 2018
|
I don't see the update on elog/download/tar/.
Do you keep builds elsewhere, perhaps on get or sourceforge?
Stefan |
|
Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:25:07 2018
|
I would like to try the new code, I don't see it on elog/download/tar/.
Do you keep updates elsewhere like on get or sourceforge?
Stefan |
|
Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:57:31 2018
|
A quick test suggests I can't just replace sprintf with snprintf.
Original error:
src/elogd.c:4503:4: note: ‘sprintf’ output between 1 and 542 bytes into a destination of size 256 [-Wformat-overflow=] |
|
Re: Compile issues on Fedora withe current elog source, posted by Andreas Luedeke on Wed Sep 12 20:52:22 2018
|
Stefan said "code is commited": that means you can download the latest version from https://bitbucket.org/ritt/elog, as described in https://elog.psi.ch/elog/download.html,
and then compile it. Clear now?
Stefan |