Focusing on Relevant Threads and Stack Frames

Filter threads and symbols to remove extraneous information and focus on your own code during a debugging session.

To focus on relevant threads and stack frames
  1. Pause your application’s execution or wait for your code to stop at a breakpoint.

  2. Use the thread filter buttons to hide threads and stack frames that are not relevant to debugging.


The debug navigator provides filter buttons for removing extraneous threads and program symbols from the debug navigator display area. With both of the highlighted buttons disabled, all threads and stackframes are shown. For example:


Enabling the left hand button, “show only stack frames,” hides threads that may not be relevant to debugging your code by suppressing the display of stack frames without debug symbols. Examples of such threads include the heartbeat and dispatch management threads and any threads that are idle and not currently executing any specific application code. Hiding these threads allows you to focus on the threads that are doing actual work for your application. For example:


The middle button, “show only crashed threads,” reduces the display to crashed threads and threads with debug symbols. Collapsing the list this way helps you focus your debugging efforts by hiding calls that are far removed from your code. For example:


The filter buttons can be used individually or in combination. The right button, “show only running blocks,” suppresses the display of non-running blocks when the debug navigator is displaying queues.