monitor: decode faults caused by UBSAN#275
Merged
Ivan-Velickovic merged 1 commit intomainfrom Feb 5, 2025
Merged
Conversation
b81e7d6 to
a421b92
Compare
In a freestanding environment on ARM64, running with LLVM's UB sanitizers will result in a `brk` instruction with a particular encoding that contains the reason UB was detected. Unfortunately, on RISC-V UBSAN just emits an unimp instruction and from what I can tell there's no way to get further information as to *why* UB was detected. Signed-off-by: Ivan-Velickovic <i.velickovic@unsw.edu.au>
a421b92 to
f4fd2b8
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.
In a freestanding environment on ARM64, running with LLVM's UB sanitizers will result in a
brkinstruction with a particular encoding that contains the reason UB was detected.Unfortunately, on RISC-V UBSAN just emits an unimp instruction and from what I can tell there's no way to get further information as to why UB was detected.
Closes #270.