Debugger
Graphical Debugger for Sublime Text for debuggers that support the debug adapter protocol
Details
Installs
- Total 18K
- Win 9K
- Mac 4K
- Linux 5K
Apr 28 | Apr 27 | Apr 26 | Apr 25 | Apr 24 | Apr 23 | Apr 22 | Apr 21 | Apr 20 | Apr 19 | Apr 18 | Apr 17 | Apr 16 | Apr 15 | Apr 14 | Apr 13 | Apr 12 | Apr 11 | Apr 10 | Apr 9 | Apr 8 | Apr 7 | Apr 6 | Apr 5 | Apr 4 | Apr 3 | Apr 2 | Apr 1 | Mar 31 | Mar 30 | Mar 29 | Mar 28 | Mar 27 | Mar 26 | Mar 25 | Mar 24 | Mar 23 | Mar 22 | Mar 21 | Mar 20 | Mar 19 | Mar 18 | Mar 17 | Mar 16 | Mar 15 | Mar 14 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 1 | 3 | 9 | 6 | 5 | 5 | 13 | 6 | 9 | 10 | 5 | 6 | 4 | 6 | 7 | 4 | 8 | 2 | 7 | 5 | 10 | 4 | 13 | 4 | 9 | 2 | 6 | 4 | 8 | 2 | 11 | 5 | 10 | 9 | 8 | 3 | 5 | 6 | 5 | 11 | 5 | 3 | 5 | 4 | 5 | 8 |
Mac | 5 | 1 | 1 | 11 | 5 | 9 | 1 | 4 | 3 | 7 | 6 | 3 | 4 | 3 | 3 | 3 | 4 | 2 | 2 | 2 | 5 | 4 | 0 | 5 | 3 | 4 | 1 | 1 | 5 | 5 | 1 | 3 | 3 | 2 | 13 | 5 | 3 | 5 | 2 | 3 | 5 | 4 | 1 | 3 | 0 | 4 |
Linux | 1 | 4 | 2 | 3 | 8 | 4 | 3 | 3 | 4 | 2 | 7 | 3 | 0 | 4 | 2 | 6 | 3 | 5 | 4 | 5 | 2 | 1 | 1 | 4 | 4 | 1 | 4 | 5 | 0 | 3 | 4 | 3 | 6 | 2 | 1 | 7 | 2 | 4 | 2 | 3 | 4 | 3 | 5 | 3 | 1 | 1 |
Readme
- Source
- raw.githubusercontent.com
Sublime Debugger
Graphical Debugger for sublime text for debuggers that support the debug adapter protocol.
Installing
Using package control run Package Control: Install Package
and select Debugger
.
or clone into your sublime Packages directory (If you are on Sublime Text 3 use the st3 branch)
Getting Started
This project attempts to match Visual Studio Code's Debugger fairly closely so their documentation can be pretty helpful. See https://code.visualstudio.com/docs/editor/debugging
Debuggers
This project comes with some pre-configured debuggers (They can be installed using Debugger: Install adapter
)
LLDB
Chrome
Firefox
Node
- For an overview see https://code.visualstudio.com/docs/nodejs/nodejs-debugging
- See https://github.com/microsoft/vscode-node-debug2
Python
- For an overview see https://code.visualstudio.com/docs/python/debugging
- See https://github.com/Microsoft/vscode-python
Go
- For an overview see https://github.com/golang/vscode-go/blob/master/docs/debugging.md
- See https://github.com/golang/vscode-go
PHP
Java
- Requires LSP and LSP-jdtls
- See https://github.com/redhat-developer/vscode-java
Emulicious Debugger
Setup
Open the debug panel
- from the command palette
Debugger: Open
- from the command palette
Install a debug adapter by running:
Debugger: Install adapter
from the command palette.Add a configuration
Debugger: Add Configuration
from the command palette (or add one manually, see below).- Configurations are added to
debugger_configurations
to your sublime-project and use the same configuration format as Visual Studio Code - Consult the debugger specific documentation links above for creating a configuration for your debugger. Most debuggers come with some configuration snippets to choose from but I highly recommend looking at the documentation for the debugger.
- Variable substitution: variables like
${file}
are supported but the list of supported variables differs from VSCode. The supported values are those listed at http://www.sublimetext.com/docs/build_systems.html#variables plus the VSCode-specific${workspaceFolder}
that resolves to the path of the first workspace folder.
- Configurations are added to
Your configuration will look something like the following but with some debugger specific fields.
"debugger_configurations" : [
{
"name" : "Name of your configuration",
"request" : "launch"|"attach",
"type" : "debugger name",
...
}
]
- Start debugging
- click the gear icon to select a configuration to use
- click the play icon to start the debugger or run
Debugger: Start
(if no configuration is selected it will ask you to select or create one)
Tasks
Tasks are based on sublime build_systems with more integration so they can be used more seamlessly while debugging. When errors occur while running a task they are reported in the debugger ui (problem detection is the same as sublime, you must add file_regex
to your task)
see https://www.sublimetext.com/docs/build_systems.html
Tasks are basically the same as sublime builds but there are a few additional parameters.
name
which will show up in the debugger UI and be the name of the panel
"debugger_tasks" : [
{
"name" : "Name of your task",
"cmd" : ["task", "command"],
...
}
]
- Tasks can be run with
Debugger: Run Tasks
- You can run tasks before and after debugging by adding
pre_debug_task
orpost_debug_task
to your configuration specifying the name of the task to run.
Settings
Settings can either be set at the project level or globally.
Project settings can be changed by appending debug.
to the setting name.
Within a .sublime_settings
file
- "open_at_startup": true
Open the debugger automatically when a project that is set up for debugging has been opened
- "ui_scale": 12
scales the entire debugger UI
Within a .sublime_project
file settings object
- debug.open_at_startup
- debug.ui_scale
for a full list of settings see debugger.sublime-settings
Troubleshooting
- Look in the debug console for errors (usually red)
- Look in the sublime console for errors
- Try the same configuration/adapter in Visual Studio Code (There is a good chance your issue is with the adapter so check out the outstanding issues for it)