Skip to content
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

bpo-40280: Enable assertions in Emscripten debug builds #29892

Closed
wants to merge 2 commits into from

Conversation

emmatyping
Copy link
Contributor

@emmatyping emmatyping commented Dec 2, 2021

Setting is documented here: https://emscripten.org/docs/porting/Debugging.html#compiler-settings

ASSERTIONS=1 is used to enable runtime checks for common memory allocation errors (e.g. writing more memory than was allocated). It also defines how Emscripten should handle errors in program flow. The value can be set to ASSERTIONS=2 in order to run additional tests.
ASSERTIONS=1 is enabled by default. Assertions are turned off for optimized code (-O1 and above).

These are useful for catching things like OOMs and such.

https://bugs.python.org/issue40280

@github-actions
Copy link

github-actions bot commented Jan 2, 2022

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the stale Stale PR or inactive for long period of time. label Jan 2, 2022
@emmatyping
Copy link
Contributor Author

This is now included in the Makefile so I think this can just be closed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting merge stale Stale PR or inactive for long period of time.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants