fjpanag opened a new pull request, #7436: URL: https://github.com/apache/incubator-nuttx/pull/7436
## Summary When `CONFIG_ARMV7M_STACKCHECK` is enabled, the function `__stack_overflow_trap()` will be called in case of a stack overflow. The problem however is that this function will immediately cause an NMI, with no information preserved about the fact. You just see the system crash, but with no way of telling why. Here, a hard-coded breakpoint is inserted, so at least during a debugging session the developer can see the root cause of the crash. I was thinking of adding and/or some prints, but I am not sure if this would be appropriate. There is a stack overflow, so better not call any other functions? ## Impact Improved debugging. ## Testing Tested a stack overflow on an STM32F4, using a JLink as a debugger. Indeed the code stops within the trap, indicating the fact of the overflow. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
