Core dump: thread names

[bertmelis]

I've got a core dump with a handful of tasks but the task names are not available except for the IDLE task. Is it possible to have the task names?

Example snippet:

===============================================================
==================== ESP32 CORE DUMP START ====================

Crashed task handle: 0x3ffbd4d4, name: '', GDB name: 'process 1073468628'

================== CURRENT THREAD REGISTERS ===================
exccause       0x1d (StoreProhibitedCause)
excvaddr       0x0
epc1           0x401469e9
epc2           0x0
epc3           0x0
epc4           0x0
epc5           0x0
epc6           0x0
eps2           0x0
eps3           0x0
eps4           0x0
eps5           0x0
eps6           0x0
[New process 1073468628]
[New process 1073548220]
[New process 1073460608]
[New process 1073427564]
[New process 1073443660]
[New process 1073601200]
[New process 1073445360]
[New process 1073431632]
[New process 1073436104]
[New process 1073610056]
[New process 1073447304]
[New process 1073547608]
[New process 1073466120]
[New process 1073409856]
[Current thread is 1 (process 1073468628)]

==================== CURRENT THREAD STACK =====================


======================== THREADS INFO =========================
pc             0x40083cb4          0x40083cb4 <panic_abort+24>
lbeg           0x4008a29d          1074307741
lend           0x4008a2bf          1074307775
lcount         0x0                 0
sar            0x8                 8
ps             0x60021             393249
threadptr      <unavailable>
br             <unavailable>
scompare1      <unavailable>
acclo          <unavailable>
acchi          <unavailable>
m0             <unavailable>
m1             <unavailable>
m2             <unavailable>
m3             <unavailable>
expstate       <unavailable>
f64r_lo        <unavailable>
f64r_hi        <unavailable>
f64s           <unavailable>
fcr            <unavailable>
fsr            <unavailable>
a0             0x8008c990          -2146907760
a1             0x3ffbec9c          1073474716
a2             0x3ffbed06          1073474822
a3             0x3ffbed33          1073474867
a4             0xa                 10
a5             0x1000              4096
a6             0x3ffbec83          1073474691
a7             0x60023             393251
a8             0x0                 0
a9             0x1                 1
a10            0x3ffbecea          1073474794
a11            0x3ffbecea          1073474794
a12            0xa                 10
a13            0x20                32
a14            0x0                 0
a15            0xa03fc000          -1606434816
Retrying reading threads information...
Retrying reading threads information...


       TCB             NAME PRIO C/B  STACK USED/FREE
---------- ---------------- -------- ----------------
0x3ffbd4d4 Corrupted TCB data
0x3ffd0bbc             IDLE1073469616/1073468988      79668/78276
0x3ffbb580                 1073459600/1073455472    1073460664/88
0x3ffb346c                 1073427056/1073424476    1073427619/84
0x3ffb734c                 1073443216/1073442620    1073443698/84
0x3ffddab0                 1073600720/1073584800    1073601232/88
0x3ffb79f0                 1073444912/1073444320    1073445413/88
0x3ffb4450                 1073431104/1073429056    1073431664/88
0x3ffb55c8                 1073435648/1073431992    1073436140/80
0x3ffdfd48                 1073615920/1073612268  1073610093/6240
0x3ffb8188                 1073422272/1073414944 1073447357/24240
0x3ffd0958                 1073609328/1073605724 1073547663/62144
0x3ffbcb08                 1073465680/1073461496    1073466175/80
0x3ffaef40                 1073556224/10735500441073409890/146776

==================== THREAD 1 (TCB: 0x3ffbd4d4, name: '') =====================


==================== THREAD 2 (TCB: 0x3ffd0bbc, name: 'IDLE') =====================
#0  0x40083cb4 in panic_abort (details=0x3ffbed06 "abort() was called at PC 0x401172cc on core 0") at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/panic.c:408
#1  0x4008c990 in esp_system_abort (details=0x3ffbed06 "abort() was called at PC 0x401172cc on core 0") at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/esp_system.c:137
#2  0x40092b40 in abort () at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/newlib/abort.c:46
#3  0x401172cf in task_wdt_isr (arg=<optimized out>) at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/task_wdt.c:176
#4  0x40085128 in _xt_lowint1 () at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/freertos/port/xtensa/xtensa_vectors.S:1114
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

==================== THREAD 3 (TCB: 0x3ffbb580, name: '') =====================
#0  0x4019c1ca in esp_pm_impl_waiti () at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_pm/pm_impl.c:849
#1  0x40117b00 in esp_vApplicationIdleHook () at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/freertos_hooks.c:63
#2  0x4008dfef in prvIdleTask (pvParameters=<optimized out>) at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/freertos/tasks.c:3987

==================== THREAD 4 (TCB: 0x3ffb346c, name: '') =====================
#0  0x40083bf4 in esp_crosscore_int_send_yield (core_id=1) at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/esp_system/crosscore_int.c:145
#1  0x4008da7c in xQueueSemaphoreTake (xQueue=0x3ffd60e4, xTicksToWait=<optimized out>) at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/hal/esp32/include/hal/cpu_ll.h:39
#2  0x40133d3c in sys_arch_sem_wait (sem=0x3ffd7208, timeout=1000) at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/lwip/port/esp32/freertos/sys_arch.c:188
#3  0x40124482 in lwip_select (maxfdp1=49, readset=0x0, writeset=0x3ffbb410, exceptset=0x0, timeout=<optimized out>) at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/lwip/lwip/src/api/sockets.c:2153
#4  0x4011a108 in esp_vfs_select (nfds=49, readfds=0x0, writefds=0x3ffbb410, errorfds=0x0, timeout=0x3ffbb418) at /Users/ficeto/Desktop/ESP32/ESP32S2/esp-idf-public/components/vfs/vfs.c:1023

[SuGlider]

Looking into the logs, it looks like an IDF application...

Thread 4 may be related to some use of a File System (VFS + Socket)...
https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/storage/vfs.html#socket-vfs-drivers

Thread 3 seems related to Power Management, which is disabled by default in ESP32 Arduino.
https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/system/power_management.html

[bertmelis]

It's not my application. My lib was used in a project but I had a concurrency bug which caused the crash.

The issue is solved but I was looking why the thread names were not printed in the log.

Maybe the memory corruption (as result of concurrency bug) caused this...?

[SuGlider]

Maybe the memory corruption (as result of concurrency bug) caused this...?

Or the application didn't set a Task Name at the execution time when it was created?