lwIP - A Lightweight TCP/IP stack - Bugs: bug #58406, MQTT example wrong call order
You are not allowed to post comments on this tracker with your current authentication level.
bug #58406: MQTT example wrong call order
Submitter: | ahmedwahdan <ahmedwahdan> | ||
Submitted: | Wed 20 May 2020 01:17:06 AM UTC | ||
Category: | apps | Severity: | 3 - Normal |
Item Group: | Crash Error | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | Planned Release: | None |
lwIP version: | 2.1.1 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-05-20 | ahmedwahdan | Carbon-Copy | - | Added -email is unavailable- |
Powered by Savane 3.13-758e.
Corresponding source code
In MQTT example, calling "mqtt_client_connec" after "mqtt_set_inpub_callback" causes the callback to be null as the client is cleared in connect function.
/* Wipe clean */
memset(client, 0, sizeof(mqtt_client_t));
Also the callback is not checked before call in "mqtt_message_received" which causes a crash.
Thank you!