Re: elog sprintf() buffer overflows on ubuntu-22, posted by Stefan Ritt on Wed Sep 25 13:19:29 2024
|
> I get the following compiler warnings about sprintf() buffer overflows. I suggest sprintf() should be replaced by std::string msprintf() from
> midas. K.O.
|
|
Re: Equation Editor does not work, posted by Nick Sauerwein on Wed Sep 25 16:00:06 2024
|
We have observed the same issue. Did the CodeCogs api change?
Thanks for the help.
Dominic |
Re: Crash on attachment upload, posted by Dominic on Tue Nov 5 15:44:57 2024
|
Does this issue occur only on Ubuntu systems? as I've experienced the same on my Raspberry Pi 5 running Ubuntu too ...
jaro
mrazek wrote:
I am on ubuntu 24.04.1, I needed to git clone, make and make install, |
|
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! |
Segfault on elog-3.1.5-1 when uploading file., posted by gary holman on Thu Dec 12 18:45:49 2024 
|
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 |
|
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. |
|
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. |
|
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 |