feat: add backtrace support #13
Merged
Conversation
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
- Add --backtrace=auto|enable|disable and thread it through target-json + linker-script rendering - Inject RUST_BACKTRACE=full into the guest env when backtrace is enabled - Add runtime .eh_frame registration support and related musl bootstrap changes - Improve host-side symbolization for low-level frames - Introduce mini-template and use it for linker/target JSON templates; drop legacy placeholder handling - Refactor cargo spike commands and update scripts/matrix - Remove zeroos-libunwind crate
zouguangxian
force-pushed
the
gx/support-backtrace
branch
from
5a4f74b to
66601a2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds backtrace support for ZeroOS guests, so panics can reliably print a usable stack backtrace (with host-side symbolization) in the Spike/unikernel environment, controlled by a single --backtrace=auto|enable|disable build-policy switch.