1# Debugger (Beta)
2
3Zed uses the Debug Adapter Protocol (DAP) to provide debugging functionality across multiple programming languages.
4DAP is a standardized protocol that defines how debuggers, editors, and IDEs communicate with each other.
5It allows Zed to support various debuggers without needing to implement language-specific debugging logic.
6This protocol enables features like setting breakpoints, stepping through code, inspecting variables,
7and more, in a consistent manner across different programming languages and runtime environments.
8
9> We currently offer onboarding support for users. We are eager to hear from you if you encounter any issues or have suggestions for improvement for our debugging experience.
10> You can schedule a call via [Cal.com](https://cal.com/team/zed-research/debugger)
11
12## Supported Debug Adapters
13
14Zed supports a variety of debug adapters for different programming languages out of the box:
15
16- JavaScript ([vscode-js-debug](https://github.com/microsoft/vscode-js-debug.git)): Enables debugging of Node.js applications, including setting breakpoints, stepping through code, and inspecting variables in JavaScript.
17
18- Python ([debugpy](https://github.com/microsoft/debugpy.git)): Provides debugging capabilities for Python applications, supporting features like remote debugging, multi-threaded debugging, and Django/Flask application debugging.
19
20- LLDB ([CodeLLDB](https://github.com/vadimcn/codelldb.git)): A powerful debugger for C, C++, Objective-C, and Swift, offering low-level debugging features and support for Apple platforms.
21
22- GDB ([GDB](https://sourceware.org/gdb/)): The GNU Debugger, which supports debugging for multiple programming languages including C, C++, Go, and Rust, across various platforms.
23
24- Go ([Delve](https://github.com/go-delve/delve)): Delve, a debugger for the Go programming language, offering both local and remote debugging capabilities with full support for Go's runtime and standard library.
25
26- PHP ([Xdebug](https://xdebug.org/)): Provides debugging and profiling capabilities for PHP applications, including remote debugging and code coverage analysis.
27
28- Ruby ([rdbg](https://github.com/ruby/debug)): Provides debugging for Ruby.
29
30These adapters enable Zed to provide a consistent debugging experience across multiple languages while leveraging the specific features and capabilities of each debugger.
31
32> Is your desired debugger not listed? You can contribute by adding support for your favorite language or debugger. Check out our [debugger extensions](extensions/debugger-extensions.md) documentation for more information.
33
34## Getting Started
35
36For basic debugging, you can set up a new configuration by opening the `New Session Modal` either via the `debugger: start` (default: f4) or by clicking the plus icon at the top right of the debug panel.
37
38For more advanced use cases, you can create debug configurations by directly editing the `.zed/debug.json` file in your project root directory.
39
40You can then use the `New Session Modal` to select a configuration and start debugging.
41
42### Launching & Attaching
43
44Zed debugger offers two ways to debug your program; you can either _launch_ a new instance of your program or _attach_ to an existing process.
45Which one you choose depends on what you are trying to achieve.
46
47When launching a new instance, Zed (and the underlying debug adapter) can often do a better job at picking up the debug information compared to attaching to an existing process, since it controls the lifetime of a whole program. Running unit tests or a debug build of your application is a good use case for launching.
48
49Compared to launching, attaching to an existing process might seem inferior, but that's far from truth; there are cases where you cannot afford to restart your program, because e.g. the bug is not reproducible outside of a production environment or some other circumstances.
50
51## Configuration
52
53While configuration fields are debug adapter-dependent, most adapters support the following fields:
54
55```json
56[
57 {
58 // The label for the debug configuration and used to identify the debug session inside the debug panel & new session modal
59 "label": "Example Start debugger config",
60 // The debug adapter that Zed should use to debug the program
61 "adapter": "Example adapter name",
62 // Request:
63 // - launch: Zed will launch the program if specified or shows a debug terminal with the right configuration
64 // - attach: Zed will attach to a running program to debug it or when the process_id is not specified we will show a process picker (only supported for node currently)
65 "request": "launch",
66 // program: The program that you want to debug
67 // This field supports path resolution with ~ or . symbols
68 "program": "path_to_program",
69 // cwd: defaults to the current working directory of your project ($ZED_WORKTREE_ROOT)
70 "cwd": "$ZED_WORKTREE_ROOT"
71 }
72]
73```
74
75All configuration fields support task variables. See [Tasks Variables](./tasks.md#variables)
76
77### Build tasks
78
79Zed also allows embedding a Zed task in a `build` field that is run before the debugger starts. This is useful for setting up the environment or running any necessary setup steps before the debugger starts.
80
81```json
82[
83 {
84 "label": "Build Binary",
85 "adapter": "CodeLLDB",
86 "program": "path_to_program",
87 "request": "launch",
88 "build": {
89 "command": "make",
90 "args": ["build", "-j8"]
91 }
92 }
93]
94```
95
96Build tasks can also refer to the existing tasks by unsubstituted label:
97
98```json
99[
100 {
101 "label": "Build Binary",
102 "adapter": "CodeLLDB",
103 "program": "path_to_program",
104 "request": "launch",
105 "build": "my build task" // Or "my build task for $ZED_FILE"
106 }
107]
108```
109
110### Automatic scenario creation
111
112Given a Zed task, Zed can automatically create a scenario for you. Automatic scenario creation also powers our scenario creation from gutter.
113Automatic scenario creation is currently supported for Rust, Go and Python. Javascript/TypeScript support being worked on.
114
115### Example Configurations
116
117#### JavaScript
118
119##### Debug Active File
120
121```json
122[
123 {
124 "label": "Debug with node",
125 "adapter": "JavaScript",
126 "program": "$ZED_FILE",
127 "request": "launch",
128 "console": "integratedTerminal",
129 "type": "pwa-node"
130 }
131]
132```
133
134##### Attach debugger to a server running in web browser (`npx serve`)
135
136Given an externally-ran web server (e.g. with `npx serve` or `npx live-server`) one can attach to it and open it with a browser.
137
138```json
139[
140 {
141 "label": "Inspect ",
142 "adapter": "JavaScript",
143 "type": "pwa-chrome",
144 "request": "launch",
145 "url": "http://localhost:5500", // Fill your URL here.
146 "program": "$ZED_FILE",
147 "webRoot": "${ZED_WORKTREE_ROOT}"
148 }
149]
150```
151
152#### Python
153
154##### Debug Active File
155
156```json
157[
158 {
159 "label": "Python Active File",
160 "adapter": "Debugpy",
161 "program": "$ZED_FILE",
162 "request": "launch"
163 }
164]
165```
166
167##### Flask App
168
169For a common Flask Application with a file structure similar to the following:
170
171```
172.venv/
173app/
174 init.py
175 main.py
176 routes.py
177templates/
178 index.html
179static/
180 style.css
181requirements.txt
182```
183
184the following configuration can be used:
185
186```json
187[
188 {
189 "label": "Python: Flask",
190 "adapter": "Debugpy",
191 "request": "launch",
192 "module": "app",
193 "cwd": "$ZED_WORKTREE_ROOT",
194 "env": {
195 "FLASK_APP": "app",
196 "FLASK_DEBUG": "1"
197 },
198 "args": [
199 "run",
200 "--reload", // Enables Flask reloader that watches for file changes
201 "--debugger" // Enables Flask debugger
202 ],
203 "autoReload": {
204 "enable": true
205 },
206 "jinja": true,
207 "justMyCode": true
208 }
209]
210```
211
212#### Rust/C++/C
213
214##### Using pre-built binary
215
216```json
217[
218 {
219 "label": "Debug native binary",
220 "program": "$ZED_WORKTREE_ROOT/build/binary",
221 "request": "launch",
222 "adapter": "CodeLLDB" // GDB is available on non arm macs as well as linux
223 }
224]
225```
226
227##### Build binary then debug
228
229```json
230[
231 {
232 "label": "Build & Debug native binary",
233 "build": {
234 "command": "cargo",
235 "args": ["build"]
236 },
237 "program": "$ZED_WORKTREE_ROOT/target/debug/binary",
238 "request": "launch",
239 "adapter": "CodeLLDB" // GDB is available on non arm macs as well as linux
240 }
241]
242```
243
244#### TypeScript
245
246##### Attach debugger to a server running in web browser (`npx serve`)
247
248Given an externally-ran web server (e.g. with `npx serve` or `npx live-server`) one can attach to it and open it with a browser.
249
250```json
251[
252 {
253 "label": "Launch Chromee (TypeScript)",
254 "adapter": "JavaScript",
255 "type": "pwa-chrome",
256 "request": "launch",
257 "url": "http://localhost:5500",
258 "program": "$ZED_FILE",
259 "webRoot": "${ZED_WORKTREE_ROOT}",
260 "sourceMaps": true,
261 "build": {
262 "command": "npx",
263 "args": ["tsc"]
264 }
265 }
266]
267```
268
269#### Go
270
271Zed uses [delve](https://github.com/go-delve/delve?tab=readme-ov-file) to debug Go applications. Zed will automatically create debug scenarios for `func main` in your main packages, and also
272for any tests, so you can use the Play button in the gutter to debug these without configuration.
273
274##### Debug Go Packages
275
276To debug a specific package, you can do so by setting the Delve mode to "debug". In this case "program" should be set to the package name.
277
278```json
279[
280 {
281 "label": "Go (Delve)",
282 "adapter": "Delve",
283 "program": "$ZED_FILE",
284 "request": "launch",
285 "mode": "debug"
286 }
287]
288```
289
290```json
291[
292 {
293 "label": "Run server",
294 "adapter": "Delve",
295 "request": "launch",
296 "mode": "debug",
297 // For Delve, the program can be a package name
298 "program": "./cmd/server"
299 // "args": [],
300 // "buildFlags": [],
301 }
302]
303```
304
305##### Debug Go Tests
306
307To debug the tests for a package, set the Delve mode to "test". The "program" is still the package name, and you can use the "buildFlags" to do things like set tags, and the "args" to set args on the test binary. (See `go help testflags` for more information on doing that).
308
309```json
310[
311 {
312 "label": "Run integration tests",
313 "adapter": "Delve",
314 "request": "launch",
315 "mode": "test",
316 "program": ".",
317 "buildFlags": ["-tags", "integration"]
318 // To filter down to just the test your cursor is in:
319 // "args": ["-test.run", "$ZED_SYMBOL"]
320 }
321]
322```
323
324##### Build and debug separately
325
326If you need to build your application with a specific command, you can use the "exec" mode of Delve. In this case "program" should point to an executable,
327and the "build" command should build that.
328
329```json
330{
331 "label": "Debug Prebuilt Unit Tests",
332 "adapter": "Delve",
333 "request": "launch",
334 "mode": "exec",
335 "program": "${ZED_WORKTREE_ROOT}/__debug_unit",
336 "args": ["-test.v", "-test.run=${ZED_SYMBOL}"],
337 "build": {
338 "command": "go",
339 "args": [
340 "test",
341 "-c",
342 "-tags",
343 "unit",
344 "-gcflags\"all=-N -l\"",
345 "-o",
346 "__debug_unit",
347 "./pkg/..."
348 ]
349 }
350}
351```
352
353##### Attaching to an existing instance of Delve
354
355You might find yourself needing to connect to an existing instance of Delve that's not necessarily running on your machine; in such case, you can use `tcp_arguments` to instrument Zed's connection to Delve.
356
357```
358{
359 "adapter": "Delve",
360 "label": "Connect to a running Delve instance",
361 "program": "/Users/zed/Projects/language_repositories/golang/hello/hello",
362 "cwd": "/Users/zed/Projects/language_repositories/golang/hello",
363 "args": [],
364 "env": {},
365 "request": "launch",
366 "mode": "exec",
367 "stopOnEntry": false,
368 "tcp_connection": { "host": "123.456.789.012", "port": 53412 }
369}
370```
371
372In such case Zed won't spawn a new instance of Delve, as it opts to use an existing one. The consequence of this is that _there will be no terminal_ in Zed; you have to interact with the Delve instance directly, as it handles stdin/stdout of the debuggee.
373
374#### Ruby
375
376To run a ruby task in the debugger, you will need to configure it in the `.zed/debug.json` file in your project. We don't yet have automatic detection of ruby tasks, nor do we support connecting to an existing process.
377
378The configuration should look like this:
379
380```json
381{
382 {
383 "adapter": "Ruby",
384 "label": "Run CLI",
385 "script": "cli.rb"
386 // If you want to customize how the script is run (for example using bundle exec)
387 // use "command" instead.
388 // "command": "bundle exec cli.rb"
389 //
390 // "args": []
391 // "env": {}
392 // "cwd": ""
393 }
394}
395```
396
397## Breakpoints
398
399To set a breakpoint, simply click next to the line number in the editor gutter.
400Breakpoints can be tweaked depending on your needs; to access additional options of a given breakpoint, right-click on the breakpoint icon in the gutter and select the desired option.
401At present, you can:
402
403- Add a log to a breakpoint, which will output a log message whenever that breakpoint is hit.
404- Make the breakpoint conditional, which will only stop at the breakpoint when the condition is met. The syntax for conditions is adapter-specific.
405- Add a hit count to a breakpoint, which will only stop at the breakpoint after it's hit a certain number of times.
406- Disable a breakpoint, which will prevent it from being hit while leaving it visible in the gutter.
407
408Some debug adapters (e.g. CodeLLDB and JavaScript) will also _verify_ whether your breakpoints can be hit; breakpoints that cannot be hit are surfaced more prominently in the UI.
409
410All breakpoints enabled for a given project are also listed in "Breakpoints" item in your debugging session UI. From "Breakpoints" item in your UI you can also manage exception breakpoints.
411The debug adapter will then stop whenever an exception of a given kind occurs. Which exception types are supported depends on the debug adapter.
412
413## Settings
414
415- `dock`: Determines the position of the debug panel in the UI.
416- `stepping_granularity`: Determines the stepping granularity.
417- `save_breakpoints`: Whether the breakpoints should be reused across Zed sessions.
418- `button`: Whether to show the debug button in the status bar.
419- `timeout`: Time in milliseconds until timeout error when connecting to a TCP debug adapter.
420- `log_dap_communications`: Whether to log messages between active debug adapters and Zed.
421- `format_dap_log_messages`: Whether to format DAP messages when adding them to the debug adapter logger.
422
423### Dock
424
425- Description: The position of the debug panel in the UI.
426- Default: `bottom`
427- Setting: debugger.dock
428
429**Options**
430
4311. `left` - The debug panel will be docked to the left side of the UI.
4322. `right` - The debug panel will be docked to the right side of the UI.
4333. `bottom` - The debug panel will be docked to the bottom of the UI.
434
435```json
436"debugger": {
437 "dock": "bottom"
438},
439```
440
441### Stepping granularity
442
443- Description: The Step granularity that the debugger will use
444- Default: line
445- Setting: debugger.stepping_granularity
446
447**Options**
448
4491. Statement - The step should allow the program to run until the current statement has finished executing.
450 The meaning of a statement is determined by the adapter and it may be considered equivalent to a line.
451 For example 'for(int i = 0; i < 10; i++)' could be considered to have 3 statements 'int i = 0', 'i < 10', and 'i++'.
452
453```json
454{
455 "debugger": {
456 "stepping_granularity": "statement"
457 }
458}
459```
460
4612. Line - The step should allow the program to run until the current source line has executed.
462
463```json
464{
465 "debugger": {
466 "stepping_granularity": "line"
467 }
468}
469```
470
4713. Instruction - The step should allow one instruction to execute (e.g. one x86 instruction).
472
473```json
474{
475 "debugger": {
476 "stepping_granularity": "instruction"
477 }
478}
479```
480
481### Save Breakpoints
482
483- Description: Whether the breakpoints should be saved across Zed sessions.
484- Default: true
485- Setting: debugger.save_breakpoints
486
487**Options**
488
489`boolean` values
490
491```json
492{
493 "debugger": {
494 "save_breakpoints": true
495 }
496}
497```
498
499### Button
500
501- Description: Whether the button should be displayed in the debugger toolbar.
502- Default: true
503- Setting: debugger.show_button
504
505**Options**
506
507`boolean` values
508
509```json
510{
511 "debugger": {
512 "show_button": true
513 }
514}
515```
516
517### Timeout
518
519- Description: Time in milliseconds until timeout error when connecting to a TCP debug adapter.
520- Default: 2000
521- Setting: debugger.timeout
522
523**Options**
524
525`integer` values
526
527```json
528{
529 "debugger": {
530 "timeout": 3000
531 }
532}
533```
534
535### Log Dap Communications
536
537- Description: Whether to log messages between active debug adapters and Zed. (Used for DAP development)
538- Default: false
539- Setting: debugger.log_dap_communications
540
541**Options**
542
543`boolean` values
544
545```json
546{
547 "debugger": {
548 "log_dap_communications": true
549 }
550}
551```
552
553### Format Dap Log Messages
554
555- Description: Whether to format DAP messages when adding them to the debug adapter logger. (Used for DAP development)
556- Default: false
557- Setting: debugger.format_dap_log_messages
558
559**Options**
560
561`boolean` values
562
563```json
564{
565 "debugger": {
566 "format_dap_log_messages": true
567 }
568}
569```
570
571## Theme
572
573The Debugger supports the following theme options:
574
575**debugger.accent**: Color used to accent breakpoint & breakpoint-related symbols
576**editor.debugger_active_line.background**: Background color of active debug line