Skip to content

[Backport release/1.16] Fix: CRYSTAL_LOAD_DEBUG_INFO=1 fails with -Dexecution_context#15715

Merged
straight-shoota merged 1 commit intorelease/1.16from
backport-15704-to-release/1.16
Apr 28, 2025
Merged

[Backport release/1.16] Fix: CRYSTAL_LOAD_DEBUG_INFO=1 fails with -Dexecution_context#15715
straight-shoota merged 1 commit intorelease/1.16from
backport-15704-to-release/1.16

Conversation

@crysbot
Copy link
Collaborator

@crysbot crysbot commented Apr 28, 2025

Automated backport of #15704 to release/1.16, triggered by a label.

Loading the debug info relies on `File` and goes through the event loop (even if reading files is blocking) which in turn requires a fiber scheduler (event loops are tied to a scheduler).

They used to be lazily instantiated, but with execution contexts it must be explicit. We thus have to load the debug info after creating the default execution context.

(cherry picked from commit 2d07222)
@crysbot crysbot added this to the 1.16.2 milestone Apr 28, 2025
@crysbot crysbot added kind:bug A bug in the code. Does not apply to documentation, specs, etc. topic:stdlib:runtime labels Apr 28, 2025
@straight-shoota straight-shoota merged commit ec9cc9c into release/1.16 Apr 28, 2025
68 of 70 checks passed
@straight-shoota straight-shoota deleted the backport-15704-to-release/1.16 branch April 28, 2025 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind:bug A bug in the code. Does not apply to documentation, specs, etc. topic:stdlib:runtime

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants