Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-04 Thread O. Hartmann
Am Sat, 3 Feb 2018 14:04:17 +0100 Dimitry Andric schrieb: > On 3 Feb 2018, at 11:43, O. Hartmann wrote: > > > > Am Tue, 30 Jan 2018 00:09:07 +0100 > > Dimitry Andric schrieb: > >> On 30 Jan 2018, at 00:01, Dimitry Andric

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-04 Thread O. Hartmann
Am Sun, 4 Feb 2018 12:28:54 +0100 "O. Hartmann" schrieb: > Am Sat, 3 Feb 2018 14:04:17 +0100 > Dimitry Andric schrieb: > > > On 3 Feb 2018, at 11:43, O. Hartmann wrote: > > > > > > Am Tue, 30 Jan 2018 00:09:07 +0100 > > >

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-03 Thread Dimitry Andric
On 3 Feb 2018, at 11:43, O. Hartmann wrote: > > Am Tue, 30 Jan 2018 00:09:07 +0100 > Dimitry Andric schrieb: >> On 30 Jan 2018, at 00:01, Dimitry Andric wrote: >>> On 29 Jan 2018, at 19:39, O. Hartmann wrote:

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-03 Thread O. Hartmann
Am Sat, 3 Feb 2018 11:43:25 +0100 "O. Hartmann" schrieb: > Am Tue, 30 Jan 2018 00:09:07 +0100 > Dimitry Andric schrieb: > > > On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > > > > > > On 29 Jan 2018, at 19:39, O. Hartmann

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-02-03 Thread O. Hartmann
Am Tue, 30 Jan 2018 00:09:07 +0100 Dimitry Andric schrieb: > On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > > > > On 29 Jan 2018, at 19:39, O. Hartmann wrote: > >> > >> Last weekend I updated a CURRENT server to recent CURRENT,

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-01-29 Thread Dimitry Andric
On 30 Jan 2018, at 00:01, Dimitry Andric wrote: > > On 29 Jan 2018, at 19:39, O. Hartmann wrote: >> >> Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and >> performed >> updates of the ports tree. Since Sunday, I receive

Re: CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-01-29 Thread Dimitry Andric
On 29 Jan 2018, at 19:39, O. Hartmann wrote: > > Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and > performed > updates of the ports tree. Since Sunday, I receive segmenatation faults (SIG > 11) when > accessing the server, especially with setup

CURRENT, CLANG 6: apache24, uid 80: exited on signal 11

2018-01-29 Thread O. Hartmann
Last weekend I updated a CURRENT server to recent CURRENT, > r328400 and performed updates of the ports tree. Since Sunday, I receive segmenatation faults (SIG 11) when accessing the server, especially with setup of nextcloud, refdb, phpldapadmin and any other access with LDAP backend (all