Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 178 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded  Show all entries    6446 Entries 
Goto page Previous  1, 2, 3 ... 177, 178, 179 ... 804, 805, 806   Next  
ID Date Icon Author Author Email Category OS ELOG Versiondown Subject Text Attachments
  68932   Tue Apr 23 14:06:36 2019 Warning Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4elogd Service exited with abnormal code: 1Dear all.

I am running elog 

elogd		   
  68933   Tue Apr 23 14:26:51 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1This kind of behavior we typically see
if some elog entry is corrupt. After a few
hours you might access this corrupt entry		   
  68942   Thu Apr 25 11:16:06 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1Thanks for the prompt feedback.

a) I confirm that the problems
shows up also when running interactively		   
  68943   Thu Apr 25 11:27:21 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1What you recommend is enough. Just make
sure to compile elogd with the flags mentioned
before, and when you get the segment violation,		   
  68951   Tue Apr 30 12:47:46 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1I was finally able to catch the crash.

I paste below the info provided
by lldb..		   
  68952   Tue Apr 30 14:07:52 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1Actually it is a little bit more difficult
than that.

I have restarted elogd and got		   
  68955   Wed May 1 10:59:59 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1Ok, that helped. It looks to me that the
strlcpy() function from MacOSC does not like
overlapping stings as parameters. Funny that		   
  68959   Thu May 2 09:47:41 2019 Reply Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1Thanks a lot for providing a quick fix!

The elog is now happily running
since two days without problems :)		   
Goto page Previous  1, 2, 3 ... 177, 178, 179 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6