Am Dienstag, Oktober 30, 2018 12:25 CET, Éric Jacquot <epjacquot@gmail.com> schrieb:
> Le ven. 26 oct. 2018 à 15:46, Stuart Henderson <stu@spacehopper.org> a écrit :
> >
> > On 2018/10/26 14:11, Éric Jacquot wrote:
> > > I don't know if it is related to the recent switch on ld LLVM, but
> > > sogo failed with current snap ((GENERIC.MP) #383: Tue Oct 23 14:44:06
> > > MDT 2018):
> >
> > This may be due to the "mmap unlock" diff which was tested in snapshots.
> > I have seen various problems with multithreaded programs including
> > segfaults and daemons silently failing to start.
> >
> > Not 100% certain that this is the problem, but it needs to be eliminated
> > as a possibility first, so please try either a newer snapshot or a
> > self-built -current kernel and let us know if it helps.
> >
>
> Hi,
>
> Tested with the 3 latest snapshots and fresh current ports :
> OpenBSD 6.4-current (GENERIC.MP) #396: Sat Oct 27 01:52:49 MDT 20
> OpenBSD 6.4-current (GENERIC.MP) #408: Sun Oct 28 23:10:11 MDT 2018
> OpenBSD 6.4-current (GENERIC.MP) #411: Mon Oct 29 19:18:32 MDT 2018
>
> sogod failed with the same issue.
Only saw that message yesterday, I updated my test VM to a recent snapsot,
and now I get the same.
I started the instance in single thread mode like this:
su - _sogo
/usr/local/sbin/sogod -WOUseWatchDog NO -WOLogFile - -WONoDetach YES
and got the exception as well.
Have to build all the gnustep stuff with debug to hopefully get something
more useful.
Sebastian
>
> Regards,
No comments:
Post a Comment