You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of the debugin with the Teensy is based on the crashReport that is generated on the Teensy when it hardfaults, and it spits out an address where it crashed in some cases and you can use addr2line on the linker file to fins the line of code that was executing at that time
It would be great if this could somehow be added either to the UI or a PIO command for faster debugging.
This would be really helpful, indeed. I use addr2line from the command-line to find the crash point, but having it built-in somehow would be really useful. (maybe something that adds a link to the detected text in serial monitor that runs the addr2line with the correct address passed in?)
Part of the debugin with the Teensy is based on the crashReport that is generated on the Teensy when it hardfaults, and it spits out an address where it crashed in some cases and you can use addr2line on the linker file to fins the line of code that was executing at that time
It would be great if this could somehow be added either to the UI or a PIO command for faster debugging.
More infio can be found about it in TD1.54 release notes under Fault Recovery & CrashReport
: https://www.pjrc.com/teensyduino-1-54-released/
The text was updated successfully, but these errors were encountered: