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
Code aborts while working with supplies #4804
Comments
From @zostayThis report is going to be a bit ugly since this code isn't published I am getting an abort while executing this program. It does not always Attached are the files required to see this problem in action. The test I am working on OS X, but I get the same result running it on in my Linux It is very likely that I've done something incorrect in my code, which is Cheers. % perl6-valgrind-m -Ilib t/http-1.0.tThis is Rakudo Perl 6 running in valgrind, a tool for debugging and ==7204== Memcheck, a memory error detector |
From @zostayPOST /index.html HTTP/1.0 a=1&b=2&c=3 |
From @zostay#!smackup use Test; my @chunk-sizes = 1, 3, 11, 101, 1009; plan @tests * @chunk-sizes * 4; for @tests -> $test { # Run the tests at various chunk sizes my @expected = $test<expected>; react { flunk 'unexpected environment received: ', %env.perl my $input = %env<p6w.input> :delete; CATCH { is $acc.decode('utf8'), $content, 'message body looks good'; LAST { QUIT { CATCH { |
From @zostayPOST /index.html HTTP/1.0 a=1&b=2&c=3 |
From @zostay |
From @zostayI've been doing some digging on this because it's basically holding up my ability to test the code I'm working on. It appears that a thread is being garbage collected, but it's aborting because pthread_mutex_destroy is returning an error code when libuv attempts to free up the thread resources. I suspect that the version of libuv used by MVM contains an old bug that is hurting my particular program. I'm continuing to dig, but my C is pretty rusty. |
From @jnthnOn Thu Dec 03 15:26:45 2015, hanenkamp wrote:
It was a mutex being garbage collected (fine) but that was still locked (not fine). MoarVM now detects when that happens and panics with a more informative error. But - more helpfully - I believe I tracked down and fixed the case where this happens. The test in S17-supply/return-in-tap.t covers it (though I suspect there were quite a few more code paths that could lead to the same problem). Since the bug was filed, many other fixes have also been applied to supplies. Since this looks very much like something I fixed yesterday, but there's no reproduction details for me to verify it, I'll resolve this; feel free to re-open or re-file (with more details if possible) if this is still an issue. Thanks, /jnthn |
The RT System itself - Status changed from 'new' to 'open' |
@jnthn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126774 (status was 'resolved')
Searchable as RT126774$
The text was updated successfully, but these errors were encountered: