New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mbedTLS causes stack overflow on some mbedOS targets #14

Closed
andresag01 opened this Issue Sep 6, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@andresag01
Contributor

andresag01 commented Sep 6, 2016

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.

@ciarmcom

This comment has been minimized.

Member

ciarmcom commented Sep 10, 2016

ARM Internal Ref: IOTSSL-969

@andresag01

This comment has been minimized.

Contributor

andresag01 commented Feb 14, 2017

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.

@RonEld

This comment has been minimized.

Contributor

RonEld commented Jun 10, 2018

I believe that #116 would resolve most of the issues raised from the benchmark application

@andresag01

This comment has been minimized.

Contributor

andresag01 commented Oct 22, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment