Debugger: Ozone 3.26b
RTOS: embOS 5.14.0.0
Compiler: gcc-arm-none-eabi-10-2020-q4-major or gcc-arm-none-eabi-7-2018-q2-update (Issue identical on with both tool chains)
Host OS: macOS Big Sur 11.6.2 or Ubuntu Linux 18.04 LTS (Issue identical on both macOS and Linux)
When I debug using Ozone, the call stack is effectively empty with only the current execution position.
There is a message "Top of stack - no unwinding symbols at <address>"
When I debug using Eclipse + Embedded C/C++ J-Link Debugging plugin + JLinkGDBServer, the call stack, local variables, global variables all work correctly.
Here is a screen shot of the Ozone Call Stack window.
Your suggestions are welcome and appreciated.
RTOS: embOS 5.14.0.0
Compiler: gcc-arm-none-eabi-10-2020-q4-major or gcc-arm-none-eabi-7-2018-q2-update (Issue identical on with both tool chains)
Host OS: macOS Big Sur 11.6.2 or Ubuntu Linux 18.04 LTS (Issue identical on both macOS and Linux)
When I debug using Ozone, the call stack is effectively empty with only the current execution position.
There is a message "Top of stack - no unwinding symbols at <address>"
When I debug using Eclipse + Embedded C/C++ J-Link Debugging plugin + JLinkGDBServer, the call stack, local variables, global variables all work correctly.
Here is a screen shot of the Ozone Call Stack window.
Your suggestions are welcome and appreciated.
The post was edited 1 time, last by morrisrx: Tested second compiler tool chain. Same problem. ().