On 2015/05/09 16:31, Philip Guenther wrote:
> On Thu, 7 May 2015, David Coppa wrote:
> > Can somebody with the necessary skills help me with this?
> >
> > $ cd /usr/ports/devel/libinotify/ && make clean fake && make test
> >
> > I remember this used to work... Now, most of the times, the
> > 'ch
> Date: Sat, 9 May 2015 16:31:25 -0700
> From: Philip Guenther
>
> On Thu, 7 May 2015, David Coppa wrote:
> > Can somebody with the necessary skills help me with this?
> >
> > $ cd /usr/ports/devel/libinotify/ && make clean fake && make test
> >
> > I remember this used to work... Now, most of
On Sat, 09 May 2015, Philip Guenther wrote:
> Looks like the problem is that while one thread is calling vfork(),
> another thread does something that acquires the spinlock inside
> rthread_dl_lock() (probably another vfork). The child of the vfork tries
> to acquire the spinlock so that it ca
On Thu, 7 May 2015, David Coppa wrote:
> Can somebody with the necessary skills help me with this?
>
> $ cd /usr/ports/devel/libinotify/ && make clean fake && make test
>
> I remember this used to work... Now, most of the times, the
> 'check_libinotify' process brings the CPU to 100% and it's st
Can somebody with the necessary skills help me with this?
$ cd /usr/ports/devel/libinotify/ && make clean fake && make test
I remember this used to work... Now, most of the times, the
'check_libinotify' process brings the CPU to 100% and it's stuck
in a sched_yield() loop:
31456/1022146 check