We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Attempting to debug a program compiled with ARM GCC in uVision.
Before the kernel is started, I am able to see the call stack for all functions. However after running the kernel only the osRtxTimerThread and osRtxIdleThread appear in the stack list, even when breaking inside a thread procedure. The same application compiled with ARMCC displays all the other threads and variables.
I have tried several compiler, debug symbols and ABI flags of the toolchain with no success. Does anyone know what prevents uVision to get the information from the application or environment to decode the stack? The RTX RTOS viewer works fine though showing all the info of the environment and kernel objects.
Thanks.