Attempt to write panics to file instead of just console. #84
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
…ith an 0x04 address on windows - deadbeef seems to make things sad
|
FYI I recently realized in my fork that using System::error instead of System::log_to_console nicely causes the simulator stop and show the error rather than close. |
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.
Not enabled in release
Attempt, on panic, to write the
PanicInfoto a local file called panic.txtPanics previously would presumably be written to the simulator console but lost forever
Part of adding this i discovered the real final panic was due to
abort_with_addrcomplaining about using a non 0x04 aligned address.Further to this i'm not really sure what
abort_with_addris meant to do, but it doesn't hurt ...