[wasm] more emscripten asserts for debug build of runtime

[pavelsavara]

-s ASSERTIONS=1 for debug build of runtime. It emits asserts to C and JS, it helps with debugging.

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.

See https://emscripten.org/docs/porting/Debugging.html

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

-s ASSERTIONS=1 for debug build of runtime. It emits asserts to C and JS, it helps with debugging.

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.

See https://emscripten.org/docs/porting/Debugging.html

Author:	pavelsavara
Assignees:	-
Labels:	arch-wasm, area-Infrastructure-mono
Milestone:	7.0.0

[radical]

Related question - would it help, or make sense to enable this for AOT/library tests?

[kg]

Makes sense to me. I agree that we might want to enable it for AOT and/or library tests.

[lewing]

Not until this doesn't break blazor

[lewing]

see dotnet/aspnetcore#37690 and #55226

[ghost]

This pull request has been automatically marked no recent activity because it has not had any activity for 14 days. It will be closed if no further activity occurs within 14 more days. Any new comment (by anyone, not necessarily the author) will remove no recent activity.

[ghost]

This pull request will now be closed since it had been marked no recent activity but received no further activity in the past 14 days. It is still possible to reopen or comment on the pull request, but please note that it will be locked if it remains inactive for another 30 days.