-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Print stack trace to brain screen on data abort #651
base: develop-pros-4
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Idea behind this PR looks good but there are a few major issues, both stylistically and content wise. I would like the trace to not be global and instead passed into the trace function via __gnu_unwind_Backtrace (source for that can be found here if you want to look at it for your reference: https://github.com/gcc-mirror/gcc/blob/master/libgcc/unwind-arm-common.inc). Feel free to ask follow up questions here or ping me on discord in our beta server or in a help post on VTOW.
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Your code also does not compile. Here is a list of the compile errors generated by the pipeline:
|
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@noam987 Do you think that the registers and the heap used and stack remaining should also be printed to the brain screen? Is there enough space to print those? If not, should they be written to a log file on the SD card, if present? |
Also, does the stacktrace contain the PC? If so, then that should save a line on the brain screen. |
Looks much better. Waiting to test this in the lab before I approve it |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Summary:
This pr prints the stack addresses to the brain screen during a data abort exception
Motivation:
This change makes it easier to debug data abort exceptions if the user is not connected to the terminal.
References (optional):
N/A
Test Plan: