pros-cli
pros-cli copied to clipboard
purduesigbots
✨ Add interactive stack trace
Summary:
Stack trace now comes with detailed description of where the program fails. This is also saved in a text file in pros-cli/pros/serial/stack_trace.txt
Motivation:
This change help ease the debug of seg faults.
References (optional):
Issue #76
Test Plan:
The code should be tested with stack traces of varied address count, and compared with output from addr2line with hot package, cold package, and monolith to make sure it doesn't omit important information (the algorithm displays addr2line output that contains the character '?' as "??", since these output are most of the time gibberish that doesn't aid debugging, but I'm not sure if this is the case ONLY for gibberish output, which can lead to the algorithm omitting useful debug information).
- [ ] test item
One thing I noticed when looking through the code is that the paths in the code use \, which is a windows only thing. The paths should be changed to use / to be platform independent.
Ignore all of the suggestions that say "Outdated". Not sure what Github just did.
Progress:
Any thought on indentation and colors?
Wonder how this would look on a small window (like the VSCode integrated terminal).
One other interesting thought, get rid of the "Registers at Exception?" section? We might want to consider shaving some of the fat that your average user may not need. Most important part is the stack trace section. (I'm fully aware addr2line provides all this data, not feasible how this is since it's been so long :skull: )
