JsDbg is a tool that provides browser developers with a web-based platform for native debugger extensions. Browser developers can use this tool to visualize large and complex data structures within the web platform, such as the DOM tree and accessibility tree. Unlike traditional debugging extensions that are debugger specific, JsDbg extensions are written with web technologies to run in the browser, which allows them to work across platforms and debuggers. By leveraging the benefits of HTML/CSS/JS, the extensions can also have richer user interfaces and functionality than what is typically present in a debugging extension.

JsDbg currently supports WinDbg and the Visual Studio debugger on Windows, and GDB on Linux. Support for additional debuggers (ex. LLDB) and platforms (ex. MacOS) will be available in the future. If you wish to use JsDbg with a debugger that is currently unsupported, please file an issue (or upvote an existing one) to track your request.

1. Download the JsDbg WinDbg extension. (This extension changes infrequently because JsDbg extensions can be updated without updating the WinDbg extension. [Last update: Jan 30th, 2019])

2. Copy jsdbg.dll into the winext folder located next your windbg.exe installation. Make sure to use the x64 version of the dll for 64-bit WinDbg, and the x86 version for 32-bit WinDbg.

1. Attach WinDbg to a running process or memory dump of Microsoft Edge/Chromium.

2. In the WinDbg command window, run !jsdbg.jsdbg, or .load jsdbg.dll followed by !jsdbg.

3. The JsDbg server will launch and prompt you to select a browser. If the debugger is attached to one browser, it is recommended that you choose a different browser for JsDbg.

1. Install the JsDbg Visual Studio (VS) extension. (This extension should be able to update without a re-install. To install the update, restart VS, use the extension once, and then restart VS again.)

1. Attach the VS debugger to a running process or memory dump of Microsoft Edge/Chromium.

2. Break into the running process using the Pause icon on the Debug toolbar, or Debug -> Break All.

3. Launch JsDbg by clicking the JS icon on the Debug toolbar, or Tools -> Launch JsDbg.

4. The JsDbg server will launch and prompt you to select a browser. If the debugger is attached to one browser, it is recommended that you choose a different browser for JsDbg.

If using Debian or Ubuntu, you can install JsDbg as a .deb package:

1. Install the .NET Core Runtime using the instructions from here.

2. Download jsdbg-gdb.deb.

3. Run apt install ./jsdbg-gdb.deb.

For other distributions, you can download a precompiled .tar.bz2. You do not need to install the .NET Core Runtime for this version.

1. Download jsdbg-gdb.tar.bz2.

2. Extract the file somewhere, e.g. in your home directory: cd ~ && tar xjf ~/Downloads/jsdbg-gdb.tar.bz2

3. Add the following snippet to your ~/.gdbinit file:

python
import sys
sys.path.insert(0, "<path where you extracted the .tar.bz2>/jsdbg-gdb")
import JsDbg
end

There is currently no autoupdate on the GDB version of JsDbg, so you have to download and install a new version manually. Just follow the installation instructions again (except for the .gdbinit part).

Last update of the GDB packages: Aug 12th, 2019.

1. Run GDB for your program as usual.

2. Type jsdbg at the GDB prompt to launch the server and open a browser window.

There are many different ways browser developers can incorporate JsDbg extensions into their debugging workflow. See JsDbg features for details about popular features in JsDbg.

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.

When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

See Contributing to JsDbg for more details about contributing to this project.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.