It doesn't sound like you're describing building a library -- maybe I'm misunderstanding something. What is known as a "component" in the ESP-IDF world, is actually a library and typically the easiest to get going if the code base is not huge (with a lot of it's own configuration). An example that ...

BTT...anyone have any advice here? Did you create a fresh ESP-IDF project and attempt to drop it in as a project local component? I don't know anything about your situation or the library you're looking to integrate with; but that's where I would start, especially if the code has never been built f...

That private event group (and a few other internals) are initialized “early” with a function attributed with `__attribute__((constructor))'. Self imposed disclaimer for those that may read that. Functions marked as `__attribute__((constructor))' are called before the task that calls app_main is eve...

I notice something.... I was mistaken about how it crashes. Inside that event handler -- these follow 2 lines always work: ip_event_got_ip_t* event = (ip_event_got_ip_t*) event_data; ESP_LOGI(TAG, "got ip:%s", ip4addr_ntoa(&event->ip_info.ip)); But the next 2 lines always crash the process s_retry_...

No change in condition..... Next, I'll remove the catch on the handler and see what happens. Well, difficult to debug this one over a forum, not looking at the big picture. So I am running short on ideas. Which probably means it's something silly I am overlooking. ;) The fact that your IP address l...

These lines are boiler plate from the standard C code example project. I can comment out all the lines inside this handler and nothing changes. I still crash when this event fires. Something behind the scenes is going on. Well the code you posted looks sane, nothing sticks out as a potential proble...

Update to this post... Here is the decode of my backtrace output: Wifi::event_handler(void*, char const*, int, void*) main/Wifi.cpp:1271 (discriminator 8) Wifi::eventMarshaller(void*, char const*, int, void*) main/Wifi.cpp:1190 handler_execute at C:/SysGCC/esp32/esp-idf/v4.0/components/esp_event/es...

For reference; I came to that conclusion as. Looking at line 204; it did indeed fail in strdup. strdup usually breaks down to a simple strlen/malloc/strcpy sequence. If the allocation failed within strdup, strdup would have failed gracefully and that would have been reported on line 205. Looking at ...

It would appear that your esp_mqtt_client_config_t structure was not initialized properly prior to calling esp_mqtt_client_init.

You will wan't to check that.

Best Regards

waterfox wrote: ↑

Mon Jun 01, 2020 5:08 pm

Oh jesus

No worries, It happens. Glad you got it worked out.

Best Regards