Component Tree

The Component Tree is a central part of the system debugger UI. It shows a hierarchical view of all objects and services exposed by the target, allowing you to explore the system’s runtime structure and navigate quickly to items of interest.

Opening the Component Tree

  • The tree will populate after a successful connection to a target.

  • If the connection is lost, the tree is cleared automatically.

Structure & Navigation

  • Root node – represents the target itself.

  • Sub‑trees – correspond to services, contexts, threads, or other components.

  • Leaf nodes – typically represent symbols or specific temu objects.

You can expand/collapse nodes with the triangle icons or by pressing ▼/→ keys when a node is selected. Typing a few letters will jump to the matching item.

Component Tree with Linux RiscV
Figure 1. Component Tree

Common Workflow

  1. Inspect a service or context

    • Locate it under the appropriate branch.

    • Hovring on the node updates the detail tooltip with additional information (properties, available actions, etc.).

  2. Follow a live context

    • When debugging a multi‑threaded target, expand the Threads branch to see each thread’s components.

    • Watching this tree while stepping lets you see new contexts created or destroyed.

  3. Search the tree

    • Enter a name or partial name to jump to the item in the tree.

    • Matching nodes are highlighted.

  4. Context menu actions

    • Right‑click a node to get operations such as View Memory, Get Register, Get Stack Trace, Disassasemble Symbol, or Get Disassembly Capabilities.

Tips

  • Double‑clicking a thread node generate the stack trace when suspended.

The component tree is read‑only; modifications must be performed via the appropriate service interface or through script commands.

With practice the Component Tree becomes an invaluable navigation aid, helping you understand the live structure of the system under inspection and quickly jump to the elements you need.== Component Tree