Getting core dump after SNTP

General
1

If you are asking a question, please follow this template:

  1. My goal is:
    Determine why getting core dump on wakeup after SNTP
  2. My actions are: [describe your actions - code, commands, etc]
    when building old builds I am finding that a core dump happens regularly
  3. The result I see is: [show the result - log, etc]
[Feb  9 16:43:44.509] mgos_mqtt_conn.c:230    MQTT0 TCP connect ok (0)
[Feb  9 16:43:44.529] mgos_sntp.c:59          SNTP reply from 216.239.35.12: time 1612917824.564943, local 1612917825.087625, delta -0.522682
[Feb  9 16:43:44.675] Guru Meditation Error: Core  1 panic'ed (LoadProhibited). Exception was unhandled.
[Feb  9 16:43:44.683] 
[Feb  9 16:43:44.683] Core  1 register dump:
  1. My expectation & question is: [describe your expectation and your question]

Is this a new problem with the mgos libraries?

as an aside one thing I noticed is that GPIO_PIN_X now need
#include “driver/gpio.h” but did not until recently

2

I noticed recently the core dumps after a sntp update with negative delta.
The origin seems to be in schedule_next_timer.

It occurs with mos latest. Building for 2.19.0 seems to be ok.

What is the result of mos debug-core-dump?

3

Thanks nliviu! I did not know about mos debug-core-dump. Sweet I will go back to 2.19.0. -Ted

4

It has been fixed.