Memory Backtrace view

This view provides backtracing capability for debugging your applications. Select an error from the Memory Problems view to display a call stack trace leading up to the selected memory issue.
Memory Backtrace view

The Memory Backtrace view lets you trace the stack for:

When you select a particular event, the Memory Backtrace view shows the event's details. If you double-click an event, the IDE highlights the corresponding source code line (if it exists):
Memory Backtrace view


Backtracing is a best effort, and may at times be inaccurate (e.g. optimized code can confuse the backtracer).

You can't currently backtrace a thread on a remote node (i.e. over Qnet).

Backtracing a corrupt stack can cause a fatal SIGSEGV because libbacktrace doesn't trap it.