Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 767 of 808  Not logged in ELOG logo
    icon2.gif   Re: Equation Editor does not work, posted by Dominic on Tue Nov 5 15:51:26 2024 
is there any update on this bug? Has anyone else observed the same problem?




Dominic
wrote:



Hi!
icon1.gif   Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 18:45:49 2024 elog-3.1.5-1-segfault-valgrind.txt
I am receiving a segfault whenever I attempt to upload a file.   Please see attached .txt for valgrind output.   This occurs in version
elog-3.1.5-1.   I reverted back to version elog-3.1.4-3 and the segfault does not occur.

Segfault occurs in Elog version: elog-3.1.5-1
    icon2.gif   Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 19:01:39 2024 
Looks like duplicate report to https://elog.psi.ch/elogs/Forum/69826




gary
holman wrote:



I am receiving a segfault whenever I attempt to upload a file.  
    icon2.gif   Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 19:01:39 2024 
Looks like duplicate report to https://elog.psi.ch/elogs/Forum/69826




gary
holman wrote:



I am receiving a segfault whenever I attempt to upload a file.  
    icon2.gif   Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Thu Dec 12 19:46:02 2024 
A statement like "core dumped" does not help much. Same with valgrind memory leaks. I need a full strack trace with all parameters when the
segment violation occurs. The easiest is when you run elogd vom inside gdb, and once you get the signal, do a "where" to see th full stack trace.

As you can see from this forum, there is absolutely no crash when you upload any file, so it must have to do with your config file or anything
    icon2.gif   Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 20:29:40 2024 
Thanks for further instructions here is full stack trace:

Program received signal SIGABRT, Aborted.
    icon2.gif   Re: Segfault on elog-3.1.5-1 when uploading file., posted by Stefan Ritt on Fri Dec 13 15:11:08 2024 
Thanks to your stack trace, I found a case where a string might get overwritten, but only if the attachment file name is longer than 256 chars. I fixed
the code and made a new RPM:

  https://www.dropbox.com/scl/fi/r37qx9aka5ytt3j7vn4km/elog-3.1.5-20241213.el8.x86_64.rpm?rlkey=knct99pdltggunrbmyr2hpfe5&st=pkre24aq&dl=0
    icon2.gif   Re: Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Fri Dec 13 19:40:57 2024 
Thanks Stefen!

I built from source (ELOG V3.1.5-3a5f2f00) and I confirmed as fixed.
 
ELOG V3.1.5-3fb85fa6