Implementing stack overflow protection for webassembly is tricky, as there are two stacks:
- The hidden webassembly stack
- The stack used for C stack objects that can have their address taken
We need to avoid overflowing either. It generally seems that the first stack is the one most vulnerable to overflow, so perhaps a simple counter would work.
@brettcannon
@hoodmane
Linked PRs
Implementing stack overflow protection for webassembly is tricky, as there are two stacks:
We need to avoid overflowing either. It generally seems that the first stack is the one most vulnerable to overflow, so perhaps a simple counter would work.
@brettcannon
@hoodmane
Linked PRs