#1812: Less Than Awesome error message when new Rakudo tries to run on old
Parrot
--------------------+-------------------------------------------------------
Reporter: masak | Owner: plobsing
Type: bug | Status: assigned
Priority: normal | Milestone:
Component: none | Version: 2.8.0
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
--------------------+-------------------------------------------------------
Comment(by plobsing):
Replying to [comment:3 masak]:
> Replying to [comment:1 plobsing]:
> > Can you submit the revs of '''both''' the compile-time and run-time
parrots? If the old parrot is no longer available (and you don't remember
the rev), the first couple hundred bytes of the PBC hexdumped might also
be useable.
>
> However, I tried just now to update Parrot to r49516 (and build it)
while keeping Rakudo fixed at 2010.09-37-g9702438. Running (the old, still
installed) Rakudo, I now get the error message
What revision is the parrot that was used to compile the old rakudo?
Knowing this is essential to understanding the problem. './perl6 -v'
should be able to tell you this.
>
{{{
$ perl6 -e 'say "OH HAI"'
OpLib must be initialized with an oplib name
}}}
>
> which also isn't very clear.
What is most likely happening here is that PMCs have become renumbered,
but PBC_COMPAT has not been bumped. Trying to read old bytecode will
attempt create and use objects which are not of the expected types.
Confusion ensues.
> I'll see if I can reproduce the circumstances that led to the original
error.
Please do, but rembember to provide:
* The revision of parrot used to compile rakudo
* The revision of parrot used to run rakudo
* The revision of rakudo
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1812#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
