I found that there is a ALTCP_MBEDTLS_LIB_DEBUG (I'm setting it to LWIP_DBG_ON) and a ALTCP_MBEDTLS_LIB_DEBUG_LEVEL_MIN (I'm setting it to 0)
I noticed that mbedtls has this function that you *may want* to set mbedtls_debug_set_threshold( ALTCP_MBEDTLS_LIB_DEBUG_LEVEL_MIN ); However, even this way, I have little or no debug from mbedtls. I have LWIP_DEBUG set, LWIP_DBG_MIN_LEVEL to LWIP_DBG_LEVEL_ALL Am I missing something? Mario Luzeiro ________________________________________ From: lwip-users <lwip-users-bounces+mrluzeiro=ua...@nongnu.org> on behalf of lwip-users-bounces+mrluzeiro=ua...@nongnu.org <lwip-users-bounces+mrluzeiro=ua...@nongnu.org> Sent: 12 July 2021 18:57 To: lwip-users@nongnu.org Subject: [lwip-users] altcp_mbedtls conf and debug Hello all, I'm trying to setup the debug on mbedtls. It looks that mbedtls debug mechanism is configured by setting the debug print function on a "conf" element, set by using the function mbedtls_ssl_conf_dbg. However looking for the lwip altcp_mbedtls interface, it looks it is creating a conf "on the fly", so the debug functions are null all the time and I can't get it work. Is somehow possible that I can setup that conf by some callback means? Is it implemented ? Mario Luzeiro _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users
