-
Benedikt Meurer authored
When opening DevTools, make sure that Wasm modules properly show up, aka are reported via "Debugger.scriptParsed" events. Previously these scripts corresponding to Wasm modules had been filtered out explicitly (accidentally). Bug: chromium:1032042 Tbr: clemensb@chromium.org Change-Id: Id5e49616a4959c9ca611dbae6f1a4e9a47413ea6 Doc: https://bit.ly/wasm-dbg-stories-2019#bookmark=id.drrsobk5mo0p Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1980588 Commit-Queue: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Mathias Bynens <mathias@chromium.org> Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Cr-Commit-Position: refs/heads/master@{#65560}
5ba9362b
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
OWNERS | ||
api-arguments-inl.h | ||
api-arguments.cc | ||
api-arguments.h | ||
api-inl.h | ||
api-natives.cc | ||
api-natives.h | ||
api.cc | ||
api.h |