Repository navigation
fix(runtime): list raising functions first in stacktraces - #24
Merged
Merged
Conversation
mremond
force-pushed
the
fm/task-8b43ec71
branch
2 times, most recently
from
November 13, 2026 20:55
27b0835 to
cca49e6
Compare
mremond
force-pushed
the
fm/task-8b43ec71
branch
from
November 14, 2026 09:13
cca49e6 to
2630950
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Native exception handlers reported an outer caller instead of the raising function because captured stacktraces used the opposite order from BEAM.
What changed
Before and after
Before: A three-function call chain returned outermost-first caught traces; self stack queries did too, and crash reports described their order incorrectly.
After: The same chain returns inner, middle, outer on native Nera and BEAM; crash reports keep that order and label it correctly.
This changes runtime stacktrace lists and terminal crash output, not a graphical view; retained execution transcripts show the results.
Checked
Live validation: Awaiting live validation. This version and evidence need an independent review of coverage and proof.
How it was checked
Ordered release runtime, compiler and workspace builds passed.
cargo clippy --workspace --all-targets --locked -- -D warnings passed.
cargo test --workspace --locked --no-fail-fast passed: 2,156 tests, one ignored.
python3 scripts/test-allocator-config.py and nera test -j 1 --timeout 30 passed: 487 native tests, two external skips.
The exact edited unit test, native stacktrace_order fixture, committed crash check and OTP 29 fixture each passed ten consecutive runs.
The existing supervisor_shutdown fixture also passed ten consecutive native runs and a direct full-output check.
Both cross-object smoke checks passed; they do not establish execution on cross targets.
Every approved per-path added and removed line is unchanged; supervisor and performance expectations match main.
Risk
Risk above low: Blast radius, medium — Exception capture, self introspection and crash printing share the frame-order invariant.
Full risk assessment