New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
segfault possibly async related #4434
Comments
From @jdvHello, The code below, when it decides to manifest (~ 1 in 10 for me at the *** Error in `/home/jdv/rakudo/install/bin/moar': double free or or Segmentation fault (core dumped) or other similar looking outputs. And here's the code: use v6; for 1..15 { my $lock = Lock.new; loop ( my $i = 0; $i < @in; $i++ ) { $lock.protect( { $cond.wait unless $done == $todo; } ); say @out; } And here's what I'm running: [jdv@wieldy ~]$ perl6 -v -jdv |
From @lizmat
Is it wise (or even sane) to use the same lock inside protected code with that lock???
|
The RT System itself - Status changed from 'new' to 'open' |
From @jnthnOn Tue Jul 28 04:48:54 2015, jdv79 wrote:
Was most likely due to the recently fixed invocation data race. I can't get it to crash at all now, so added a test to S17-lowlevel/lock.t. /jnthn |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#125705 (status was 'resolved')
Searchable as RT125705$
The text was updated successfully, but these errors were encountered: