1. 10 Mar, 2022 1 commit
  2. 28 Apr, 2020 1 commit
    • Paolo Severini's avatar
      Wasm debugging with LLDB: access Wasm engine state · 74e93186
      Paolo Severini authored
      This changelist makes the GDB-stub actually execute GDB-remote commands, by
      accessing the Wasm engine state. More precisely:
      - class GdbServer registers DebugDelegates that receive debug notifications when
        a new Wasm module is loaded, when execution suspends at a breakpoint or for an
        unhandled exception.
      - Since the GDB-remote commands arrive on a separate thread, all
        queries from the debugger are transformed into Task objects, that are posted
        into a TaskRunner that runs in the Isolate thread.
      - class WasmModuleDebug contains the logic to retrieve the value of globals, locals, memory ranges from the
        Wasm engine and to add/remove breakpoints.
      
      Build with: v8_enable_wasm_gdb_remote_debugging = true
      Run with: --wasm-gdb-remote
      Test with: python tools\run-tests.py --outdir=out\debug_x64 debugging -j 1
      
      Bug: chromium:1010467
      Change-Id: I9703894620a027d3c920926db92e2ff809d84ab8
      Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1941139Reviewed-by: 's avatarBenedikt Meurer <bmeurer@chromium.org>
      Reviewed-by: 's avatarClemens Backes <clemensb@chromium.org>
      Commit-Queue: Paolo Severini <paolosev@microsoft.com>
      Cr-Commit-Position: refs/heads/master@{#67412}
      74e93186
  3. 19 May, 2017 1 commit
    • Andreas Haas's avatar
      [wasm] Cleanup the wasm fuzzer corpus files. · 2f92e9eb
      Andreas Haas authored
      In a recent CL I moved the corpus of the wasm fuzzer and of the
      wasm-asmjs fuzzer to a different directory
      (wasm_corpus and wasm_asmjs_corpus) so that the corpus is not executed
      on the try-bots. With this CL I remove the old corpus from the
      .gitignore file.
      
      In addition I removed the hooks for wasm_corpus and
      wasm_asmjs_corpus from the V8 DEPS file, because in a V8 checkout
      they are not used anyway.
      
      I also added code to the test runner to delete all *.wasm files
      from the directories test/fuzzer/wasm and test/fuzzer/wasm_asmjs.
      This code should be removed in a week, but it will help my coworkers
      to cleanup their V8 checkout.
      
      
      
      R=bradnelson@chromium.org
      CC=machenbach@chromium.org
      
      Change-Id: I9fdf9d77b71b133f84f7e744763d65fdf127d624
      Reviewed-on: https://chromium-review.googlesource.com/505614
      Commit-Queue: Andreas Haas <ahaas@chromium.org>
      Reviewed-by: 's avatarMichael Achenbach <machenbach@chromium.org>
      Cr-Commit-Position: refs/heads/master@{#45417}
      2f92e9eb
  4. 24 Oct, 2016 1 commit
  5. 29 Aug, 2016 1 commit
  6. 14 Mar, 2016 1 commit
  7. 11 Mar, 2016 1 commit
    • mstarzinger's avatar
      [testing] Convert some "preparser" tests into "message". · 57ef4f4f
      mstarzinger authored
      This converts existing "preparser" tests that expect a certain exception
      message to be produced into "message" tests. Thereby we get much better
      coverage because the former test suite degraded by now to just check
      whether each test case threw or not, the exception message was not being
      checked at all.
      
      This also deprecates the ability of "preparser" to specify that single
      test cases based on JS files are expected to throw, "messages" is far
      superior, use that test suite instead.
      
      R=machenbach@chromium.org
      TEST=message,preparser
      
      Review URL: https://codereview.chromium.org/1784013003
      
      Cr-Commit-Position: refs/heads/master@{#34713}
      57ef4f4f
  8. 27 Jul, 2012 1 commit
  9. 23 Jul, 2012 2 commits
  10. 18 Jul, 2012 1 commit