NCS: How to analyze Zephyr error messages to find out fault locations?

[Changhai Liao]

zephyr.map ：https://drive.google.com/file/d/1W_K_Xn3eTuYPf9KmQNoMDgCWsSsuPhHK/view?usp=sharing 

[00:09:09.260,284] <inf> nordic_dfu_ble: limit link timer = 0x20002f0c
[00:09:09.268,188] <err> pal_abort: Aborting from thread: ?
[00:09:09.274,566] <err> os: r0/a1:  0x00000004  r1/a2:  0x00000040  r2/a3:  0x000000e0
[00:09:09.283,325] <err> os: r3/a4:  0x00000000 r12/ip:  0x0001ac61 r14/lr:  0x00026123
[00:09:09.291,961] <err> os:  xpsr:  0x61000000
[00:09:09.297,180] <err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000
[00:09:09.307,647] <err> os: s[ 4]:  0x00000000  s[ 5]:  0x0000cd3e  s[ 6]:  0x00000000  s[ 7]:  0x00000000
[00:09:09.318,023] <err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000
[00:09:09.328,399] <err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000
[00:09:09.338,958] <err> os: fpscr:  0x00000000
[00:09:09.344,146] <err> os: Faulting instruction address (r15/pc): 0x00033894
[00:09:09.352,020] <err> os: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
[00:09:09.359,710] <err> os: Current thread: 0x200040b8 (unknown)
[00:09:09.366,607] <err> fatal_error: Resetting system

[Susheel Nuguru]

This topic has been discussed a lot both in devzone and other external blogs. 

This one for example seems to be inline with your query of debugging path for a fault on zephyr..