{{ }}

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!

Issues with Callstack Window display


Callstack Window doesn't show current call stack content or displayed info is incorrect.

Possible solutions: 

Compiler optimization

Compiler can optimize the code to an extent that the required information being used by the debugger to extract the Call Stack context is not available or just not sufficient. Check the compiler manual for any relevant compiler switches and try to decrease compiler optimization level(s) - at least for test to confirm that this is the root cause for Call Stack not being displayed properly.

Call Stack Generation

Call Stack can be generated using information from different sources: ELF file, CPU EABI, or by code simulation. 

Automated is the default option and winIDEA will automatically determine the best method.

1. Open Debug / Configure Session / Applications / Symbol Files.

2. Select the download file and press Edit.

3. Click Advanced to open the Edit Options dialog.

4. From the drop-down Call Stack Generation field select:

  • EABI - Call Stack is generated as specificated in the EABI documentation for specific architecture.
  • using .debug_frame - ELF debug_frame section will be used to unwind the stack.
  • Simulated - Call Stack is reconstructed by using object-code simulation.

ARM Cortex-M

Check the topic How to get maximum Call Stack information?

Was this answer helpful?

Sorry this article didn't answer your question, we'd love to hear how we can improve it.
Note: This form won't submit a case. We'll just use it to make this article better.

Similar topics

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No similar topics found!

Other topics in the same category

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!