runtime: improve hardfault handler and stack reporting on Cortex-M#5380
Open
digitalentity wants to merge 1 commit into
Open
runtime: improve hardfault handler and stack reporting on Cortex-M#5380digitalentity wants to merge 1 commit into
digitalentity wants to merge 1 commit into
Conversation
- Add reference to the current goroutine stack (PSP) when showing the hardfault info on Cortex-M.
digitalentity
force-pushed
the
de_better_hardfault_handler
branch
from
63dc7f7 to
217664b
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
1 participant
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.
Add reference to the current goroutine stack (PSP) when showing the hardfault info on Cortex-M. The stack where the hardfault happens is usually the scheduler's stack (MSP), which provides no information about the goroutine that actually caused the fault.
This was required to debug random crashes (#5375). The reason was stack overflow, which trigered the
udfinstruction. The MSP only pointed to the HardFault handler and the PC initially suggested stack corruption and nil dereference, while in reality the stack canary was overwritten which triggered a panic.