Re: [perl #123434] [SEGV] CounterMutexSingleton sample crashes

2017-02-23 Thread Ryan Bastic
Indeed :) It was just a simple test case to demonstrate some things to ab5tract. Thanks for your work! On Thu, Feb 23, 2017 at 11:53 AM, Timo Paulssen via RT < perl6-bugs-follo...@perl.org> wrote: > Hi, > > we've put in an improved error message for when libuv refuses to create an > eventloop fo

Re: [perl #123434] [SEGV] CounterMutexSingleton sample crashes

2017-02-23 Thread Ryan Bastic
Sounds good! Thanks. On Thu, Feb 23, 2017 at 12:21 PM, Timo Paulssen via RT < perl6-bugs-follo...@perl.org> wrote: > Now the exception also contains the error as reported by libuv: > > timo@schmand /tmp> perl6 CounterMutexSingleton.pl6 --num_threads=253 > Could not create a new Thread: to

Re: [perl #123434] [SEGV] CounterMutexSingleton sample crashes

2016-07-27 Thread Ryan Bastic
Hi, I'm pretty sure this is related to not mutexing / synchronizing around shared resource usage of STDOUT, etc. In talking with Jonathan before, this seemed to be a likely cause. Adding synchronization primitives around the mutexed usage of the print() command fixed it previously, if memory serv