31b23fcbd8
We currently do not report a script ID for wasm code, i.e. the script id is 0. We cannot just print the script ID itself, as it is considered unstable. Thus this CL only makes us print whether it is set or not. In a follow-up CL where we fix setting script IDs for wasm code events the output will change. R=thibaudm@chromium.org Bug: chromium:1125986 Change-Id: Ibc52829ea8a5a5c9506e36390eb4c608bcab4624 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2571120 Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/master@{#71616} |
||
---|---|---|
.. | ||
console-profile-end-parameterless-crash-expected.txt | ||
console-profile-end-parameterless-crash.js | ||
console-profile-expected.txt | ||
console-profile-wasm-expected.txt | ||
console-profile-wasm.js | ||
console-profile.js | ||
coverage-block-expected.txt | ||
coverage-block.js | ||
coverage-expected.txt | ||
coverage.js | ||
enable-disable-expected.txt | ||
enable-disable.js | ||
record-cpu-profile-expected.txt | ||
record-cpu-profile.js | ||
stop-without-preceeding-start-expected.txt | ||
stop-without-preceeding-start.js |