ESP32 Forum

ESP32 Official Forum
http://esp32.io/

Coredump info is incomplete

http://esp32.io/viewtopic.php?f=2&t=1142

Page 1 of 1

Coredump info is incomplete

Posted: Thu Feb 09, 2017 1:22 am
by xzwang
I have enabled the config of coredump and print it on UART. However the Coredump info is incomplete, and it can't be analysed by espcoredump.py. I got the coredump info with the "CORE DUMP START", but there is no "CORE DUMP END". The followed info is what I have gotten.

Code: Select all

Guru Meditation Error: Core  0 panic'ed (Unhandled debug exception)
Debug exception reason: BREAK instr
Register dump:
PC      : 0x00000000  PS      : 0x00000016  A0      : 0x80019fb8  A1      : 0x3ffc0550
A2      : 0x4d4d4d4d  A3      : 0x3fff0000  A4      : 0x060b4610  A5      : 0x00000022
A6      : 0x000023f0  A7      : 0x3ffc06c8  A8      : 0x80156a6c  A9      : 0x5a5a5a5b
A10     : 0x00000001  A11     : 0x00000262  A12     : 0x00000069  A13     : 0x3ffc0640
A14     : 0x00000001  A15     : 0xffffffff  SAR     : 0x00000017  EXCCAUSE: 0x00000001
EXCVADDR: 0x00000000  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0xffffffff

Backtrace: 0x00000000:0x3ffc0550 0x40019fb8:0x3ffc0570 0x40046686:0x3ffc05a0 0x40047518:0x3ffc05c0 0x40048536:0x3ffc05e0 0x40082831:0x3ffc0600 0x40054ed9:0x3ffc0620 0x40083015:0x3ffc0640 0x400811f0:0x3ffc0670

================= CORE DUMP START =================
VFIBABAAAABkAQAA
wEP9P3BC/T+0Q/0/
cEL9P1BD/T8zlWAAoFf8P6BX/D/AQ/0/mFf8PwEAAABgF/0/YBf9P8BD/T8AAAAA
GAAAALgz/T9idENvbnRyb2xsZXIAbN0AAAAAALRD/T8AAAAAIAQGABgAAAAAAAAA
AAAAAAAAAAAAAAAAIAL9P4gC/T/wAv0/AAAAAAAAAAABAAAAAAAAAPBZQD8AAAAA
SB0AQAAAAAAAAAAAAAAAAIAQ/T8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
...
...
...
AAAAAAEAAAAAAAAAAAAAAFAAMAACAAIpAAAAAAAAAAAAAAAAAAAAAAIA4P4AAAAA
AAAAAAAAAAAAAAABMFUIQNRfCEDQIwhAxCMIQLBWCECwIwhAnCMIQHQjCECQIwhA
XCMIQEQjCEDMEQ1A//8/swIAAAD//wAAAAAAAAAAAAAAAAAAAâ–’ets Jun  8 2016 00:22:57

rst:0x7 (TG0WDT_SYS_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
Does anyone know why the coredump info is incomplete?
Thanks.

Re: Coredump info is incomplete

Posted: Thu Feb 09, 2017 3:59 am
by ESP_Sprite
It looks like for some reason, dumping the core took long enough for a watchdog to trigger. We merged a fix for that bug three days ago; can you try pulling esp-idf and then see if the problem is still there?

Re: Coredump info is incomplete

Posted: Fri Feb 10, 2017 1:15 am
by xzwang
Coredump info is complete after IDF updated.
Thanks.

But I am wonder how to analysis the core info like this:

Code: Select all

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

================== CURRENT THREAD REGISTERS ===================
pc             0x400d12e8	0x400d12e8 <esp_vApplicationIdleHook+40>
lbeg           0x0	0
lend           0x0	0
lcount         0x0	0
sar            0x0	0
ps             0x60820	395296
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             0x40083e74	1074282100
a1             0x3ffd3020	1073557536
a2             0x8	8
a3             0x3ffc2a50	1073490512
a4             0x1	1
a5             0x0	0
a6             0x1	1
a7             0x3ffd1388	1073550216
a8             0x3ffc2a6c	1073490540
a9             0x0	0
a10            0x0	0
a11            0x0	0
a12            0x14	20
a13            0xa5	165
a14            0xa5	165
a15            0x3ffd1194	1073549716

==================== CURRENT THREAD STACK =====================
#0  0x400d12e8 in esp_vApplicationIdleHook () at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/esp32/./freertos_hooks.c:52
#1  0x40083e74 in prvIdleTask (pvParameters=0x0) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./tasks.c:3294

======================== THREADS INFO =========================
  Id   Target Id         Frame 
  16   process 15        0x400854a6 in xQueueGenericReceive (xQueue=0x3ffc2a24 <s_ipc_sem>, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  15   process 14        0x400854a6 in xQueueGenericReceive (xQueue=0x3ffc6990, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  14   process 13        0x400854a6 in xQueueGenericReceive (xQueue=0x3ffc764c <xphyQueue>, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  13   process 12        0x400854a6 in xQueueGenericReceive (xQueue=0x3ffc68cc <s_event_queue>, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  12   process 11        0x400854a6 in xQueueGenericReceive (xQueue=0xffffffff, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  11   process 10        0x400854a6 in xQueueGenericReceive (xQueue=0x3ffc68b8 <xBtuQueue>, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  10   process 9         0x400854a6 in xQueueGenericReceive (xQueue=0x3ffc6754 <xHciHostQueue>, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  9    process 8         0x400854a6 in xQueueGenericReceive (xQueue=0xffffffff, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  8    process 7         0x400854a6 in xQueueGenericReceive (xQueue=0x3ffc3a58, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  7    process 6         0x400854a6 in xQueueGenericReceive (xQueue=0x3ffd1b98, pvBuffer=0x3ffee064, xTicksToWait=0, xJustPeeking=0) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  6    process 5         0x400854a6 in xQueueGenericReceive (xQueue=0x0, pvBuffer=<unavailable>, xTicksToWait=<unavailable>, xJustPeeking=<unavailable>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  5    process 4         0x400854a6 in xQueueGenericReceive (xQueue=0x3ffd199c, pvBuffer=0x3ffd4550, xTicksToWait=2148017817, xJustPeeking=1074275312) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
  4    process 3         0x40085c70 in prvProcessTimerOrBlockTask (xNextExpireTime=1073486592, xListWasEmpty=<optimized out>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./timers.c:469
  3    process 2         0x40083dec in vTaskDelay (xTicksToDelay=<optimized out>) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./tasks.c:1407
  2    process 1         0x400854a6 in xQueueGenericReceive (xQueue=0x3ffc5bc0 <mbox>, pvBuffer=0x3ffd4ff0, xTicksToWait=2148450475, xJustPeeking=1073503168) at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/freertos/./queue.c:1594
* 1    <main task>       0x400d12e8 in esp_vApplicationIdleHook () at /cygdrive/d/VM/share/ESP32/esp-idf_master/components/esp32/./freertos_hooks.c:52

======================= ALL MEMORY REGIONS ========================
Name   Address   Size   Attrs
.rtc.text 0x400c0000 0x0 RW  
.iram0.vectors 0x40080000 0x400 R XA
.iram0.text 0x40080400 0x1d850 R XA
.dram0.data 0x3ffc0000 0x2018 RW A
.flash.rodata 0x3f400010 0x312c8 RW A
.flash.text 0x400d0018 0x91bb4 R XA
.coredump.tasks 0x3ffd15d0 0x164 RW 
.coredump.tasks 0x3ffd2f60 0x16c RW 
.coredump.tasks 0x3ffd50c4 0x164 RW 
.coredump.tasks 0x3ffd4f60 0x158 RW 
.coredump.tasks 0x3ffefe4c 0x164 RW 
.coredump.tasks 0x3ffefd70 0xd0 RW 
.coredump.tasks 0x3ffd1830 0x164 RW 
.coredump.tasks 0x3ffd3400 0x214 RW 
.coredump.tasks 0x3ffd4628 0x164 RW 
.coredump.tasks 0x3ffd44d0 0x14c RW 
.coredump.tasks 0x3ffef4d8 0x164 RW 
.coredump.tasks 0x3ffef390 0x13c RW 
.coredump.tasks 0x3ffee364 0x164 RW 
.coredump.tasks 0x3ffee040 0x318 RW 
.coredump.tasks 0x3ffecbf4 0x164 RW 
.coredump.tasks 0x3ffecaf0 0xf8 RW 
.coredump.tasks 0x3fff2d64 0x164 RW 
.coredump.tasks 0x3fff2c60 0xf8 RW 
.coredump.tasks 0x3fff1dcc 0x164 RW 
.coredump.tasks 0x3fff1cd0 0xf0 RW 
.coredump.tasks 0x3fff4a50 0x164 RW 
.coredump.tasks 0x3fff4950 0xf4 RW 
.coredump.tasks 0x3fff0d08 0x164 RW 
.coredump.tasks 0x3fff0c00 0xfc RW 
.coredump.tasks 0x3ffd63d0 0x164 RW 
.coredump.tasks 0x3ffd62b0 0x114 RW 
.coredump.tasks 0x3ffec198 0x164 RW 
.coredump.tasks 0x3ffec080 0x10c RW 
.coredump.tasks 0x3ffd7290 0x164 RW 
.coredump.tasks 0x3ffd7190 0xf4 RW 
.coredump.tasks 0x3ffd0c74 0x164 RW 
.coredump.tasks 0x3ffd0b80 0xe8 RW 

===================== ESP32 CORE DUMP END =====================
===============================================================
Done!
The crash happened situation:
1,ESP32 connect to AP as STA.
2,after several hours, Uart print SYSTEM_EVENT_STA_DISCONNECTED repeatedly.
3,ESP32 crashed.

How to confirm which task make the crash? It looks like not my app caused this crash.
Can you give me some suggestion? Thanks.

Re: Coredump info is incomplete

Posted: Fri Feb 10, 2017 1:41 am
by kolban
Might this help? It is a tutorial on using the core dump functions to determine where within code a panic occurred.

http://esp32.com/viewtopic.php?f=18&t=1111
All times are UTC
Page 1 of 1
Powered by phpBB® Forum Software © phpBB Limited
https://www.phpbb.com/