Repository navigation
Reverts Backtrace: format to what it used to be (IDFGH-7580) - #9138
Merged
Merged
Conversation
Was: Backtrace: N:M N:M N:M ... Now: Backtrace:N:MN:M N:M ... The problem with the new format is that it is hard to parse and breaks the parser that is used by PlatformIO. The old format is much more reasonable. I do not see how the pattern in IDFDUT.py can work with the new format, due to the missing space after the :
|
|
github-actions
Bot
changed the title
MitchBradley
added a commit
to MitchBradley/platform-espressif32
that referenced
this pull request
Jun 11, 2022
Recent versions of ESP-IDF have a bug in which the Backtrace: line is malformed. Old/Good: Backtrace: 0xN:0xM 0xN:0xM 0xN:0xM ... New/Bad: Backtrace:0xN:0xM0xN:0xM 0xN:0xM ... I issued espressif/esp-idf#9138 against ESP-IDF to fix the underlying problem, but it is unclear when or if that PR will be accepted, especially since the monitor program in ESP-IDF is immune to the problem. By using a decoding technique similar to the one in ESP-IDF's monitor, either backtrace format can be accepted. Supersedes platformio#687 , which does not quite work, in that it misses one of the entries.
MitchBradley
added a commit
to bdring/FluidNC
that referenced
this pull request
Jun 12, 2022
platformio.ini was inadvertently asking for the esp32 exception decoder filter to be loaded twice into the pio monitor program, causing problems with exception decoding. This patch makes it load only once, which helps with, but does not by itself solve, exception decoding problems. For the other necessary fixes, see espressif/esp-idf#9138 and platformio/platform-espressif32#831 The first one is the correct fix to the root problem, while the second one is a pragmatic short-term workaround.
Collaborator
|
Thanks for your contribution. |
MitchBradley
added a commit
to bdring/FluidNC
that referenced
this pull request
Jun 13, 2022
platformio.ini was inadvertently asking for the esp32 exception decoder filter to be loaded twice into the pio monitor program, causing problems with exception decoding. This patch makes it load only once, which helps with, but does not by itself solve, exception decoding problems. For the other necessary fixes, see espressif/esp-idf#9138 and platformio/platform-espressif32#831 The first one is the correct fix to the root problem, while the second one is a pragmatic short-term workaround.
ivankravets
pushed a commit
to platformio/platform-espressif32
that referenced
this pull request
Jun 16, 2022
Recent versions of ESP-IDF have a bug in which the Backtrace: line is malformed. Old/Good: Backtrace: 0xN:0xM 0xN:0xM 0xN:0xM ... New/Bad: Backtrace:0xN:0xM0xN:0xM 0xN:0xM ... I issued espressif/esp-idf#9138 against ESP-IDF to fix the underlying problem, but it is unclear when or if that PR will be accepted, especially since the monitor program in ESP-IDF is immune to the problem. By using a decoding technique similar to the one in ESP-IDF's monitor, either backtrace format can be accepted. Supersedes #687 , which does not quite work, in that it misses one of the entries.
Collaborator
|
Hello @MitchBradley, |
espressif-bot
added
Resolution: NA
Collaborator
|
Hello @MitchBradley, |
3 tasks done
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
5 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.
Was: Backtrace: N:M N:M N:M ...
Now: Backtrace:N:MN:M N:M ...
The problem with the new format is that it is hard to parse and
breaks the parser that is used by PlatformIO. The old format
is much more reasonable. I do not see how the pattern in IDFDUT.py
can work with the new format, due to the missing space after the :
Possible fix for #8722