You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added ability to inspect coredumps with the inspect_state.py script for
post-mortem inspection of the system state at the time of a crash.
Signed-off-by: Trond F. Christiansen <trond.christiansen@nordicsemi.no>
Copy file name to clipboardExpand all lines: docs/common/tooling_troubleshooting.md
+8-3Lines changed: 8 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -382,10 +382,12 @@ When enabling immediate logging, it might be necessary to increase the stack siz
382
382
383
383
### State Inspection Script
384
384
385
-
The `inspect_state.py` script allows you to inspect the current state of the application's state machines and internal data structures on a running device.
386
-
It connects to the device via J-Link, parses the ELF file to find symbol locations and types, and reads the memory to display the current state.
385
+
The `inspect_state.py` script allows you to inspect the current state of the application's state machines and internal data structures on a running device. It suport two modes of operation:
387
386
388
-
This is particularly useful for debugging when the application is stuck or behaving unexpectedly, and you want to see the exact state of each module without halting the CPU or adding extensive logging.
387
+
- **Live Inspection**: It connects to the device via J-Link, parses the ELF file to find symbol locations and types, and reads the memory to display the current state.
388
+
- **Coredump Analysis**: It can also analyze a coredump file generated by the device, allowing you to inspect the state at the time of the crash.
389
+
390
+
This is particularly useful for debugging when the application is stuck or behaving unexpectedly, and you want to see the exact state of each module without halting the CPU or adding extensive logging, or when analyzing crashes.
389
391
390
392
**Prerequisites:**
391
393
@@ -402,7 +404,10 @@ This is particularly useful for debugging when the application is stuck or behav
402
404
Run the script from the `scripts` directory (or adjust the path), providing the path to your ELF file and optionally the J-Link device name:
0 commit comments