Feedback
Feedback

If you are having issues with the exercises, please create a ticket on DevZone: devzone.nordicsemi.com
Drag & Drop Files, Choose Files to Upload You can upload up to 2 files.

Traces and issues

From traces to issues

When a device uploads diagnostic data describing a crash or fault, that single occurrence is called a trace. Because the same underlying bug typically produces many structurally identical traces across your fleet, nRF Cloud computes a signature for each trace, derived from things like the error code, the active thread, its backtrace, and the software type, and groups traces sharing a signature into a single issue. In other words: a trace is one instance of a problem, and an issue is the bug itself, as seen across every device and every time it occurred.

This grouping is what makes a fleet of thousands of devices tractable to debug. You triage a small list of issues instead of an unbounded stream of individual crash reports, while still being able to open any issue and see every trace that contributed to it.

Inspecting issue- and trace-level detail

Opening an issue gets you the aggregate view: how many traces, across how many devices, across which software and hardware versions. Opening an individual trace within that issue gets you forensic detail nRF Cloud extracted from that one occurrence, which typically includes:

  • Threads and backtraces: the call stack for every thread running at the time of the fault, with the faulting thread listed first. Each frame can be expanded for source location, line number, and address.
  • Exception info: a decoded, human-readable explanation of the fault registers, rather than raw hex you’d otherwise have to decode by hand.
  • Registers and locals: the register and local-variable state for whichever stack frame you have selected in the thread view.
  • Globals and statics: global and static variable state at the moment of the crash, including the ability to cast an untyped pointer to a concrete type if you know what it should point to.
  • Logs: whatever logs were captured around the time of the trace, giving you the narrative context leading up to the crash.

Note

The amount of data reported depends on the storage space available on the device in noinit RAM or NVM (e.g. flash) for crash data. nRF Cloud will by default prioritize the active thread in data collection.

Switch language?

Progress is tracked separately for each language. Switching will continue from your progress in that language or start fresh if you haven't begun.

Your current progress is saved, and you can switch back anytime.

Register an account
Already have an account? Log in
(All fields are required unless specified optional)

  • 8 or more characters
  • Upper and lower case letters
  • At least one number or special character

Forgot your password?
Enter the email associated with your account, and we will send you a link to reset your password.