Note that since not all memory is saved in core dump only values of variables allocated on stack will be meaningfulįor more information about core dump internals see the - Core dump internals Configurations User can examine memory, variables and tasks states manually. Idf.py coredump-debug - creates core dump ELF file and runs GDB debug session with this file. ![]() Idf.py coredump-info - prints crashed task’s registers, callstack, list of available tasks in the system, memory regions and contents of memory stored in core dump (TCBs and stacks) It is also possible dumping variables content onĭemand if previously attributed accordingly.ĮSP-IDF provides special commands to help users to retrieve and analyse core dumps: So it is possible to find out what task, at what instruction (line of code) and what callstack of that task lead to the crash. Snapshots include tasks control blocks (TCB) and stacks. Core dump contains snapshots of all tasks in the system at the moment of failure. ![]() User can choose to generate core dump in order to analyse Upon the crash system enters panic state, prints some information and halts or reboots depending configuration. ![]() This useful technique allows post-mortem analysis of software state at the moment of failure. Running idf.py coredump-info and idf.py coredump-debugĮSP-IDF provides support to generate core dumps on unrecoverable software errors.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |