Fix: Report malloc failures in target_description of cortexm, cortexar #1902
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.
Detailed description
Discovered during testing around July 14. Triggerable by PR1830 (stack front) plus no PR1529 (traceswoasync on heap) on stlink/swlink. (hits even harder with ENABLE_RTT=1). Otherwise the symptom on attach is rather cryptic, GDB gets no (or malformed) register description and defaults to wrong architecture and register numbers (use RSP logging).
May also be beneficial not just to ENABLE_DEBUG=1 builds, but also out-of-tree projects which have RTOS and log channels but a small heap for userspace tasks.
Your checklist for this pull request
Closing issues