| Age | Commit message (Collapse) | Author |
|---|
|
This usually shows up in custom sections, containing plain bytes.
|
|
It was arbitrary, it's still arbitrary, but now it's funny too :^)
|
|
|
|
It's possible for the module to request too many locals, we now reject
such modules instead of trying to allocate space for them.
The value itself is chosen arbitrarily, so future tweaks _might_ be
necessary.
Found by OSS-Fuzz: https://oss-fuzz.com/testcase?key=4755809098661888
|
|
This way, we can make sure that it doesn't overflow when ASAN is
enabled.
|
|
|
|
This makes debugging wasm code a bit easier, as we now know what fails
instead of just "too bad, something went wrong".
|
|
These limits are described in the spec, and we're supposed to stop
execution at some point.
The limits are arbitrarily chosen.
|
|
These allow a very basic memory-using program to work.
|
|
This can currently parse a really simple module.
Note that it cannot parse the DataCount section, and it's still missing
almost all of the instructions.
This commit also adds a 'wasm' test utility that tries to parse a given
webassembly binary file.
It currently does nothing but exit when the parse fails, but it's a
start :^)
|
