TianlongLiang 6fd8001eb6 Update CIs and documents to make naming of generated binaries consistent (#1823) %!s(int64=3) %!d(string=hai) anos
..
darwin 6eaf779a2d Install patched LLDB on vscode extension activation (#1637) %!s(int64=3) %!d(string=hai) anos
linux 0a08b92662 VSCode-Extension: Add empty platform directories (#1460) %!s(int64=3) %!d(string=hai) anos
windows 0a08b92662 VSCode-Extension: Add empty platform directories (#1460) %!s(int64=3) %!d(string=hai) anos
README.md 6fd8001eb6 Update CIs and documents to make naming of generated binaries consistent (#1823) %!s(int64=3) %!d(string=hai) anos

README.md

If you want to enable source debugging for this extension and use your own patched lldb, please build lldb firstly following this instruction

After building(linux for example), create bin folder and lib folder respectively in linux directory, add following necessary target files into the folders

/llvm/build-lldb/bin/lldb # move this file to {VS Code directory}/resource/debug/linux/bin/
/llvm/build-lldb/bin/lldb-vscode # move this file to {VS Code directory}/resource/debug/linux/bin/
/llvm/build-lldb/lib/liblldb.so.13 # move this file to {VS Code directory}/resource/debug/linux/lib/

If you are debugging this extension following this tutorial, {VS Code directory} will be {WAMR root directory}/test-tools/wamr-ide/VSCode-Extension. If you want to replace the current lldb with your own patched version so that you can use your patched lldb in VS Code, {VS Code directory} will be ~/.vscode/extensions/wamr.wamride-1.1.2 or ~/.vscode-server/extensions/wamr.wamride-1.1.2.

Note: For macOS, the library is named like liblldb.13.0.1.dylib.

Then you can start the extension and run the execute source debugging by clicking the debug button in the extension panel.