Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefan Ritt on Fri Dec 16 09:27:26 2016 
|
Still no luck. Tried your URL and still works fine for me:
|
|
Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefan Ritt on Fri Dec 16 09:55:20 2016
|
Ok I found it!
Was tricky. In my development environment (XCode) it worked fine. Only when I compiled elogd under Sierra on the command line, the probelm occured.
That's why I did not see it earlier. It has to do with some functions Apple apparently changed ("strlcpy"). These function now have a new |
Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefano Bonaldo on Fri Dec 16 14:44:19 2016
|
Bug FIXED! Many thanks Stefan and my warmest congratulations for the elog project.
Stefano
|
|
Re: elogd complains about unknown cookies, posted by Stefan Ritt on Fri May 22 13:59:41 2015
|
> elogd is spewing these messages about unknown cookies:
>
> Received unknown cookie "is_returning"
|
|
Re: elogd complains about unknown cookies, posted by Konstantin Olchanski on Sat May 23 02:49:22 2015
|
> > elogd is spewing these messages about unknown cookies:
> >
> > Received unknown cookie "is_returning"
|
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Tue Apr 23 14:26:51 2019
|
This kind of behavior we typically see if some elog entry is corrupt. After a few hours you might access this corrupt entry by accident, and then the
server stops. If you see however this behavior on a fresh logbook with no corrupt entries, then the problem must lie somewhere else.
Do you see the same problem running under linux? |
|
Re: elogd Service exited with abnormal code: 1, posted by Alessio Sarti on Thu Apr 25 11:16:06 2019
|
Thanks for the prompt feedback.
a) I confirm that the problems shows up also when running interactively the elog through elogd -p 8080
b) I am trying to catch the exit using lldb on the mac machine. I will be able to give you some feedback on that I hope in the next week (not |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Thu Apr 25 11:27:21 2019
|
What you recommend is enough. Just make sure to compile elogd with the flags mentioned before, and when you get the segment violation, do a stack trace
inside the debugger to learn where the fault happend. Maybe also print the contents of some variables at the current location.
Stefan |