| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[debug][wasm] Fix GDB remote server compilation errors Fix compilation errors and test failures in the GDB remote server stub when enabled through v8_enable_wasm_gdb_remote_debugging. The GDB remote server stub has been broken for a long time due to V8 API changes. This patch addresses multiple issues: - Fix type conversions from internal Isolate* to v8::Isolate* - Update Handle to DirectHandle for WasmInstanceObject and WasmTrustedInstanceData - Fix WasmModuleObject API calls (module() -> native_module()->module()) - Add Zone/AccountingAllocator for more efficient memory management - Update include headers for changed APIs - Fix unit tests to work with current V8 codebase This enables native debuggers like GDB and LLDB to attach to V8 and debug WebAssembly modules when the GDB remote debugging flag is enabled. Bug: 433881953 Change-Id: Ib2d728b0e954d8701076a2ff07e59336794ddf82 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6785387 Reviewed-by: Paolo Severini <paolosev@microsoft.com> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#101856} | 10 个月前 | |
buganizer: fix component IDs in DIR_METADATA This only matches the old monorail components. Bug: 341800538 Change-Id: Id74fbdb3b9be0c858b77af84966c6c37adf78c5c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6025833 Reviewed-by: Michael Achenbach <machenbach@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Paul Semel <paulsemel@chromium.org> Commit-Queue: Paul Semel <paulsemel@chromium.org> Cr-Commit-Position: refs/heads/main@{#97252} | 1 年前 | |
Add DIR_METADATA files to v8. Generate DIR_METADATA files and remove metadata from OWNERS files for v8. R=jkummerow@chromium.org, ochang@chromium.org, yangguo@chromium.org Bug: chromium:1113033 Change-Id: I82cbb62e438d82dbbc408e87120af39fa9da0afa Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2476680 Reviewed-by: Adam Klein <adamk@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Yang Guo <yangguo@chromium.org> Commit-Queue: Edward Lesmes <ehmaldonado@chromium.org> Auto-Submit: Edward Lesmes <ehmaldonado@chromium.org> Cr-Commit-Position: refs/heads/master@{#70669} | 5 年前 | |
Wasm debugging with LLDB: access Wasm engine state 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/+/1941139 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#67412} | 6 年前 | |
Wasm debugging with LLDB: access Wasm engine state 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/+/1941139 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#67412} | 6 年前 | |
Wasm debugging with LLDB: access Wasm engine state 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/+/1941139 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#67412} | 6 年前 | |
[debug][wasm] Fix GDB remote server compilation errors Fix compilation errors and test failures in the GDB remote server stub when enabled through v8_enable_wasm_gdb_remote_debugging. The GDB remote server stub has been broken for a long time due to V8 API changes. This patch addresses multiple issues: - Fix type conversions from internal Isolate* to v8::Isolate* - Update Handle to DirectHandle for WasmInstanceObject and WasmTrustedInstanceData - Fix WasmModuleObject API calls (module() -> native_module()->module()) - Add Zone/AccountingAllocator for more efficient memory management - Update include headers for changed APIs - Fix unit tests to work with current V8 codebase This enables native debuggers like GDB and LLDB to attach to V8 and debug WebAssembly modules when the GDB remote debugging flag is enabled. Bug: 433881953 Change-Id: Ib2d728b0e954d8701076a2ff07e59336794ddf82 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6785387 Reviewed-by: Paolo Severini <paolosev@microsoft.com> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#101856} | 10 个月前 | |
[debug][wasm] Fix GDB remote server compilation errors Fix compilation errors and test failures in the GDB remote server stub when enabled through v8_enable_wasm_gdb_remote_debugging. The GDB remote server stub has been broken for a long time due to V8 API changes. This patch addresses multiple issues: - Fix type conversions from internal Isolate* to v8::Isolate* - Update Handle to DirectHandle for WasmInstanceObject and WasmTrustedInstanceData - Fix WasmModuleObject API calls (module() -> native_module()->module()) - Add Zone/AccountingAllocator for more efficient memory management - Update include headers for changed APIs - Fix unit tests to work with current V8 codebase This enables native debuggers like GDB and LLDB to attach to V8 and debug WebAssembly modules when the GDB remote debugging flag is enabled. Bug: 433881953 Change-Id: Ib2d728b0e954d8701076a2ff07e59336794ddf82 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6785387 Reviewed-by: Paolo Severini <paolosev@microsoft.com> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#101856} | 10 个月前 | |
[debug][wasm] Fix GDB remote server compilation errors Fix compilation errors and test failures in the GDB remote server stub when enabled through v8_enable_wasm_gdb_remote_debugging. The GDB remote server stub has been broken for a long time due to V8 API changes. This patch addresses multiple issues: - Fix type conversions from internal Isolate* to v8::Isolate* - Update Handle to DirectHandle for WasmInstanceObject and WasmTrustedInstanceData - Fix WasmModuleObject API calls (module() -> native_module()->module()) - Add Zone/AccountingAllocator for more efficient memory management - Update include headers for changed APIs - Fix unit tests to work with current V8 codebase This enables native debuggers like GDB and LLDB to attach to V8 and debug WebAssembly modules when the GDB remote debugging flag is enabled. Bug: 433881953 Change-Id: Ib2d728b0e954d8701076a2ff07e59336794ddf82 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6785387 Reviewed-by: Paolo Severini <paolosev@microsoft.com> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#101856} | 10 个月前 | |
Wasm debugging with LLDB: access Wasm engine state 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/+/1941139 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#67412} | 6 年前 | |
Wasm debugging with LLDB: access Wasm engine state 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/+/1941139 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#67412} | 6 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 10 个月前 | ||
| 1 年前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 6 年前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 6 年前 | ||
| 6 年前 |