You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The stack requirements for mbed TLS largely depend on the configuration used at compile time. However, there are no stack memory consumption figures available to help users decide on an appropriate stack size for embedded applications. As a result, it is very common that mbed TLS causes stack overflow errors that may or may not the caught by the system depending on the severity of the issue.
The text was updated successfully, but these errors were encountered:
Currently, some of the example applications use the mbed_app.json file to set the macro OS_MAINSTKSIZE and increase the stack size. However, I do not think this has the desired effect in the latest mbed OS version. This should be removed from the examples.
Indeed, the stack issues should now be resolved with #116, #194 and other refactoring PRs for authcrypt and tls-client. So this issue can now be closed.
The stack requirements for mbed TLS largely depend on the configuration used at compile time. However, there are no stack memory consumption figures available to help users decide on an appropriate stack size for embedded applications. As a result, it is very common that mbed TLS causes stack overflow errors that may or may not the caught by the system depending on the severity of the issue.
The text was updated successfully, but these errors were encountered: