enhanced stack trace decoder for ESP8266 #3013
Open
pljakobs wants to merge 1 commit intoSmingHub:developfrom
Open
enhanced stack trace decoder for ESP8266 #3013pljakobs wants to merge 1 commit intoSmingHub:developfrom
pljakobs wants to merge 1 commit intoSmingHub:developfrom
Conversation
…2 side (mostly for consistency). This also updates gdb_hooks to include the register dump into the portion the user is to copy in to the stack trace decoder
PR Summary
|
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
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.
plus minor fixes on the ESP32 side (mostly for consistency). This also updates gdb_hooks to include the register dump into the portion the user is to copy in to the stack trace decoder
The output, when used interactively, uses a pager and the input now requires to mark the end of the input by ^D (what was necessary to not get mixed lines in the output)
I did change the gdb_hooks.cpp file to
gdbstub_exception_handler_flash()anddumpExceptionInfo()functions. This might not be the most elegant way, but with the=======lines only wrapping around the actual stack dump, the guidance is confusing for the user and they would probably not copy the register file