Page 1 of 1

Stack smashing protect failure! ()

Posted: Wed Jan 24, 2024 10:21 pm
by Gan-Erdene
Most of the time my device works well, but after a day, it stops and shows an error. Turning it off and on again fixes it for a day. What's the difference between a soft reset and a hard reset? What might be causing this issue?
ELF file SHA256: 1353dc90dc68e50e
Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1184
load:0x40078000,len:13220
ho 0 tail 12 room 4
load:0x40080400,len:3028
entry 0x400805e4

Stack smashing protect failure!


abort() was called at PC 0x400ed208 on core 1


Backtrace: 0x40083cad:0x3ffbf8ec |<-CORRUPTED




ELF file SHA256: 1353dc90dc68e50e

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x12 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1184
load:0x40078000,len:13220
ho 0 tail 12 room 4
load:0x40080400,len:3028
entry 0x400805e4

Re: Stack smashing protect failure! ()

Posted: Thu Jan 25, 2024 3:51 am
by ESP_Sprite
Probably something like allocating a buffer on the stack, then overflowing that buffer.