Understanding Traces vs Coredumps

What are Coredumps vs Trace Events

Coredumps capture a detailed snapshot of the system's state, including registers, memory, and the call stack. On the other hand, Trace Event is a more lightweight version that captures only the program counter, return address, and call stack.

How to Identify Coredump vs Trace Events

We can distinguish between Coredumps and Trace Events in two ways:

• Via the Traces Tab: Navigate to a specific device, click on the Traces tab, and look for the Source Type column. This will indicate whether the trace is a Coredump or an Event
• Via the Individual Trace: Click on a specific Trace. Next to the State and Log Files tabs, you'll see the Source Type, which will be either Coredump or Event.

When to Use Coredumps vs Trace Events

We recommend capturing a full Coredump when the system encounters a fatal problem, such as a hard fault. However, there may be situations where capturing a Coredump is not desirable or possible:

• If stopping and rebooting the system is not an option
• If the error is recoverable, but you still want to understand how often it occurs.

In such cases, Trace Events can be a helpful alternative.

Please follow the links below for more information:

• Trace Events
• Coredumps