segmentation fault when "restrict edit" is used and "new" is allowed for anonymous users, posted by Andreas Luedeke on Mon Jun 20 05:31:31 2011 
|
The simple config file below produces a segmentation fault when elogd is started,
http://localhost/Test/?cmd=New
is opened in the browser and then e.g. "Entry" is switched to "Problem".
|
Re: segmentation fault when "restrict edit" is used and "new" is allowed for anonymous users, posted by Stefan Ritt on Mon Jun 20 17:53:58 2011
|
You are the first one allowing guests to enter new entries, so this probes a code path which was never used before. I fixed the crash in SVN revision 2416,
but it might be that there are more issues with that. Just keep reporting. |
|
Elog crashes with URL find npp=0, posted by Andreas Luedeke on Tue Sep 13 11:54:16 2011
|
Some user wanted to modify the URL by hand and succeeded to crash the elogd process with npp=now
It appears that npp=0 crashes elogd with the following error message:
|
Re: Elog crashes with URL find npp=0, posted by Andreas Luedeke on Tue Sep 13 13:38:19 2011
|
> [...] It appears that npp=0 crashes elogd [...]
Here's a patch: search for "npp" in src/elogd.c and add the following line:
|
elogd crash for special query, posted by Andreas Luedeke on Thu Oct 27 11:29:08 2011
|
A query to a logbook can crash the demon.
Query:
|
|
ELOG deamon stuck in find_thread_head(), posted by soren poulsen on Sat Apr 30 19:45:30 2011
|
ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to a different logbook and the deamon just
gets stuck.
If I restart the daemon, the message was in fact moved: I can move it back to its original destination without problems. |
|
Re: ELOG deamon stuck in find_thread_head(), posted by Soren Poulsen on Tue May 3 17:35:57 2011
|
soren poulsen wrote:
ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to |
Re: ELOG deamon stuck in find_thread_head(), posted by Soren Poulsen on Wed Jul 6 12:06:01 2011
|
Soren Poulsen wrote:
|