Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 199 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Categoryup OS ELOG Version Subject Text Attachments
  68839   Tue Sep 11 19:46:40 2018 Warning Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Compile issues on Fedora withe current elog sourceTried compiling on FC27 and 28, both result
in binaries but with serious issues; writing
data larger than then allowed.
  
  68840   Wed Sep 12 11:10:18 2018 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceThis warning is triggered by the use of
the sprintf() funciton, which can write beyond
the boundary of the destination string. I
  
  Draft   Wed Sep 12 15:20:11 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceI don't see the update on elog/download/tar/.
Do you keep builds elsewhere, perhaps
on get or sourceforge?
  
  68842   Wed Sep 12 15:25:07 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceI would like to try the new code, I don't
see it on elog/download/tar/.
Do you keep updates elsewhere like
  
  68843   Wed Sep 12 15:57:31 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceA quick test suggests I can't just
replace sprintf with snprintf.
Original error:
  
  68844   Wed Sep 12 20:52:22 2018 Reply Andreas Luedekeandreas.luedeke@psi.chBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceStefan said "code is commited":
that means you can download the latest version
from https://bitbucket.org/ritt/elog, as
  
  68845   Thu Sep 13 06:12:59 2018 Reply Allen TuttleAllenEmail@wavecable.comBug reportLinux3.1.3Re: Compile issues on Fedora withe current elog sourceLatest compile effort on Fedora 28 using
the bitbucket source downloaded at 21:12
PDT:
  
  68851   Fri Oct 26 08:56:59 2018 Warning Wenhao Huangwhyellow@mail.sdu.edu.cnBug reportLinuxELOG V3.1.2-bd7messy code for chinese charactorThe Chinese character appears messy code.
The encoding way is the default utf-8. How
can I solve this problem?
  
ELOG V3.1.5-2eba886