In my opinion, your two cases should be resolved like this:

1. Disabling heap usage in WolfMQTT: While WolfMQTT uses dynamic memory allocation through WOLFMQTT_MALLOC, the library doesn't have a built-in option to entirely avoid heap usage. However, you can modify the behavior by redefining WOLFMQTT_MALLOC, WOLFMQTT_FREE, and WOLFMQTT_REALLOC macros to use static memory or pre-allocated buffers. This would allow you to run the library without relying on heap memory.
                                          geometry dash meltdown
2. TLS and WolfSSL (WOLFSSL_NO_MALLOC): Yes, your understanding is correct. The WOLFSSL_NO_MALLOC configuration is meant to disable heap usage. However, not all malloc calls are guarded by this macro, so while it reduces dynamic memory usage, you may still need to review the code and ensure that no heap allocations occur where WOLFSSL_NO_MALLOC isn't applied. In this case, you can manually replace or adjust these calls to use static memory.

Regard,
joedavenportjd25