Для этого сайта требуется поддержка JavaScript.
Обзор
Помощь
Регистрация
Вход
microsoft
/
vscode-js-debug
зеркало из
https://github.com/microsoft/vscode-js-debug.git
Следить
1
В избранное
0
Форкнуть
Вы уже форкнули vscode-js-debug
0
Код
Задачи
Пакеты
Проекты
Релизы
Вики
Активность
connor4312/wasm-2
vscode-js-debug
/
.nvmrc
2 строки
3 B
Plaintext
Исходник
Постоянная ссылка
Обычный вид
История
Убрать экранирование
Экранировать
feat: initial DWARF debugger integration Enables stepping around and setting breakpoints in native code. Variables represenation is still a todo, and this needs some polish. It refactors the `Source.sourceMap` into a more generic location provider, which may be backed by the new IWasmSymbols interface. This then talks to the DWARF debugger. The SourceContainer's `_sourceMaps` are also now just folded into the `Source.sourceMap`; that information was duplicate and the only benefit was deduplication if two sources had the same sourcemap, but this is really rare. This also made all location mapping asynchronous, so there were a few refactors around there, too. It also refactors how I implemented WAT (text format decompilation) last iteration. That previously "pretended" the source of the WASM was WAT, but this caused issues because the location transformation we did on the scripts is done before location mapping. So instead, the WAT is an extra fake 'file' in the symbols and we resolve any unknown locations into the WAT file. One that that _doesn't_ work yet is entrypoint breakpoints for wasm, which means that breakpoints set before the debug session starts may be missed. I have a thread out to the Chromium folks to see if there's a solution to this. For #1789
2023-09-16 02:35:07 +03:00
18