1

(3 replies, posted in wolfSSL)

Thanks for following up and this addresses the issue.

Joe

2

(3 replies, posted in wolfSSL)

I'm running the MQX port of version wolfSSL embedded SSL 2.8.0.  I've noticed when a session is closed an error in thrown by MQX for trying to free a NULL pointer.  It appers the wolfSSL library frees memory twice after the handshake (FreeHandshakeResources()) and after the session is closed (SSL_ResourceFree()).  MQX can be built to remove this check, which could result in some bad behavior.  I've addressed the problem by checking the pointer before XFREE is called.  Is this known behavior and is it expected that the free routine should catch NULL pointers?

Thanks