Problem with failing primitiveStringHash? | Cannot load metacello.sar
See original GitHub issueI tried to file in this metacello.sar
in two images, Squeak5.3-19448-32bit.image
and a fresh 64-bit Trunk image. In each case, I get the following error message while the preamble of the SAR file is processed:
MessageNotUnderstood: ByteString>>bitAnd:
ByteString(Object)>>doesNotUnderstand: #bitAnd:
ByteString(String)>>hashWithInitialHash:
ByteString>>hashWithInitialHash:
MCMethodDefinition>>hash
Set>>scanFor:
A closer look at the temporary variables causes confusion:
- in
String>>hashWithInitialHash:
and below,speciesHash
contains the receiver - in
MCMethodDefinition>>hash
,hash
isnil
- When I restart from
MCMethodDefinition>>hash
and step over all sends, the error does not occur - But when I restart and step over from the sender of this context (
Set>>scanFor:
), the error occurs again
So, is there a bug in primitiveStringHash
that probably misaligns the stack variables in any way? Interesting bug …
PS: Please let me know if you can reproduce it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
metacello-work/MetacelloScriptingAPI.md at master - GitHub
Metacello loads the packages and dependencies (required projects) for a project based on the specifications in the configuration of a project.
Read more >how to install a specific metacello group from command line in ...
I don't know why is failing (it shouldn't), but you can workaround the problem by executing: ./pharo bootstrap.image eval --save " Metacello ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
So ca63f69 checks the stack after every primitive. And 4e152a6 fixes an embarrassing number of primitives that left the stack imbalanced or at least did not check
argCount
. Released as 1.0.1.@LinqLover please use the vm-dev list for this kind of question/discussion. Nobody’s gonna read through closed tickets 😉