Skip to content
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

Attempt to parallelize a program produces "Internal Error: Unwound entire stack and missed handler" #3652

Closed
p6rt opened this issue Jan 24, 2015 · 4 comments
Labels

Comments

@p6rt
Copy link

p6rt commented Jan 24, 2015

Migrated from rt.perl.org#123666 (status was 'rejected')

Searchable as RT123666$

@p6rt
Copy link
Author

p6rt commented Jan 24, 2015

From @moritz

I try to (partially) parallelize htlmify.p6 from
https://github.com/perl6/doc and this is what I got​:

Internal Error​: Unwound entire stack and missed handler

This is commit f17ca342f434a160d455b9d16f7d4a2d17279087 of perl6/doc,
and perl6-m --version says​:
This is perl6 version 2015.01-5-g912a7fa built on MoarVM version
2015.01-5-ga29eaa9

This happens on a 64bit Debian Jessie Linux (sorry, "GNU/Linux" :-), on
hack.p6c.org. Shell accounts are available for anybody who wants to
debug this.

@p6rt
Copy link
Author

p6rt commented May 21, 2016

From @smls

I tried reproducing this on current Rakudo, so I checked out the specified old revision of the perl6/doc repo, and tried to run its htmlify.p6.

At first I got a bunch of errors due to the code not conforming to language changes that were made since 2015.01. Various tweaks (`MONKEY-SEE-NO-EVAL`, `unit`, `uniq`->`unique`, etc.) made them go away.

But now I get​:

  Method 'sub' not found for invocant of class 'Array'
  in block at /home/sam/dev/src/p6doc/lib/Perl6/TypeGraph.pm line 80

Instead of spending more effort to try and fix the code for current Rakudo until it either runs fine or reproduces the stated concurrency error, I'm inclined to just close this ticket.

A lot has changed in Rakudo's concurrency support over the last 16 months, so chances are the issue is no longer relevant.
If the bug still exists, a new ticket (hopefully with a golfed test-case) can be opened.

Thoughts?

@p6rt
Copy link
Author

p6rt commented May 21, 2016

The RT System itself - Status changed from 'new' to 'open'

@p6rt p6rt closed this as completed May 21, 2016
@p6rt
Copy link
Author

p6rt commented May 21, 2016

@smls - Status changed from 'open' to 'rejected'

@p6rt p6rt added the conc label Jan 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant