foster/denoland-deno
1
0
Fork 0
mirror of https://github.com/denoland/deno.git synced 2024-12-15 03:48:02 -05:00
Code Issues Packages 1 Wiki Activity
denoland-deno/cli/tests/testdata/run/wasm_unreachable.js

10 lines
380 B
JavaScript
Raw Normal View History

fix: WebAssembly runtime error propagation (#6137) Currently WebAssembly runtime errors don't propagate up to the user as they use urls to denote where the error occurred which get caught by the source-map pipeline which doesn't support the wasm scheme.
2020-06-11 11:03:27 -04:00
// WebAssembly module containing a single function with an unreachable instruction
refactor: move out test files from root testdata directory into sub directories (#15949)
2022-09-19 10:32:21 -04:00
const binary = await Deno.readFile("./assets/unreachable.wasm");
fix: WebAssembly runtime error propagation (#6137) Currently WebAssembly runtime errors don't propagate up to the user as they use urls to denote where the error occurred which get caught by the source-map pipeline which doesn't support the wasm scheme.
2020-06-11 11:03:27 -04:00
const module = new WebAssembly.Module(binary);
const instance = new WebAssembly.Instance(module);
feat: Show the URL of streaming WASM modules in stack traces (#12268) WebAssembly modules compiled through `WebAssembly.compile()` and similar non-streaming APIs don't have a URL associated to them, because they have been compiled from a buffer source. In stack traces, V8 will use a URL such as `wasm://wasm/d1c677ea`, with a hash of the module. However, wasm modules compiled through streaming APIs, like `WebAssembly.compileStreaming()`, do have a known URL, which can be obtained from the `Response` object passed into the streaming APIs. And as per the developer-facing display conventions in the WebAssembly Web API spec, this URL should be used in stack traces. This change implements that.
2021-10-10 10:03:23 -04:00
// Compare the stack trace with wasm_url.js, which compiles the WASM module with
// streaming APIs.
fix: WebAssembly runtime error propagation (#6137) Currently WebAssembly runtime errors don't propagate up to the user as they use urls to denote where the error occurred which get caught by the source-map pipeline which doesn't support the wasm scheme.
2020-06-11 11:03:27 -04:00
instance.exports.unreachable();
Copy permalink