Fix crash when gpio:stop/0 or gpio:close/1 are used on ESP32

Fixes a hard vm crash when either `gpio:stop/0` or `gpio:close/1` are used on
ESP32 platform, which emits the following error before dumping a stacktrace
(ESP-IDF native, not an erlang stacktrace) in `idf.py monitor`:

assert failed: tlsf_free tlsf.c:1119 (!block_is_free(block) && "block already marked as free")

closes #816

Signed-off-by: Winford <[email protected]>

Author: UncleGrumpy

CHANGELOG.md

@@ -11,6 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - ESP32: fix i2c_driver_acquire and i2c_driver_release functions, that were working only once.
 - Sending messages to registered processes using the `!` operator now works.
 - Fixed bug in `OP_SEND` that would accept sending a message to any integer or term without raising an error.
+- ESP32: fixed bug in `gpio:stop/0` and `gpio:close/1` that would cause the VM to crash.
 
 ## [0.6.0-beta.0] - 2024-02-08
 

src/platforms/esp32/components/avm_builtins/gpio_driver.c

@@ -275,7 +275,7 @@ static term gpiodriver_close(Context *ctx)
             struct GPIOListenerData *gpio_listener = GET_LIST_ENTRY(item, struct GPIOListenerData, gpio_listener_list_head);
             gpio_num = gpio_listener->gpio;
             list_remove(&gpio_listener->gpio_listener_list_head);
-            list_remove(&gpio_listener->listener.listeners_list_head);
+            sys_unregister_listener(ctx->global, &gpio_listener->listener);
             free(gpio_listener);
 
             gpio_set_intr_type(gpio_num, GPIO_INTR_DISABLE);
@@ -287,6 +287,7 @@ static term gpiodriver_close(Context *ctx)
         }
     }
 
+    ctx->platform_data = NULL;
     globalcontext_unregister_process(glb, gpio_atom_index);
     free(gpio_data);