Paolo Severini 135b15a6bd [wasm] [debugging] Fix --wasm-gdb-remote ... The GDB-stub for Wasm debugging (which builds with the flag v8_enable_wasm_gdb_remote_debugging) doesn't build anymore after a few changes in the interface of wasm::DebugInfo. This CL fixes the build, and also adds a few small changes to the protocol. Change-Id: I250a8c86fd83048434e68cbdc5cb8ae243577393 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2571341 Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Philip Pfaffe <pfaffe@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#71669}		2020-12-08 19:37:25 +00:00
..
test_files	[wasm] [debugging] Fix --wasm-gdb-remote	2020-12-08 19:37:25 +00:00
breakpoints.py	Wasm debugging with LLDB: access Wasm engine state	2020-04-28 01:02:32 +00:00
connect.py	Wasm debugging with LLDB: access Wasm engine state	2020-04-28 01:02:32 +00:00
DIR_METADATA	Add DIR_METADATA files to v8.	2020-10-20 22:12:28 +00:00
float.py	Wasm debugging with LLDB: access Wasm engine state	2020-04-28 01:02:32 +00:00
gdb_rsp.py	[wasm] [debugging] Fix --wasm-gdb-remote	2020-12-08 19:37:25 +00:00
memory.py	[wasm] [debugging] Fix --wasm-gdb-remote	2020-12-08 19:37:25 +00:00
OWNERS	Add DIR_METADATA files to v8.	2020-10-20 22:12:28 +00:00
status.py	Wasm debugging with LLDB: access Wasm engine state	2020-04-28 01:02:32 +00:00
stepping.py	Wasm debugging with LLDB: access Wasm engine state	2020-04-28 01:02:32 +00:00
trap.py	Wasm debugging with LLDB: access Wasm engine state	2020-04-28 01:02:32 +00:00