Mixed-mode execution exposes an unusual bug #2629
Well this is a first...we have a bug that only manifests when running in mixed mode.
Something inside RubyGems is breaking when running under mixed-mode execution that works in pure-interpreter or pure-jit. I dug into it a bit, and it looks like variables are getting munged, probably due to call protocols not aligning correctly. I have not dug into it any further.
This is the cause of -Pmain failure right now. You can run the short version via:
You'll get the same
What I Know
I tracked the problem as far as Gem.try_activate, which calls find_inactive_path and find_by_path. Those eventually get to BasicSpecification#contains_requirable_file?, and then here things started to go screwy. The
That's about all I have.
The text was updated successfully, but these errors were encountered: