1# Using a debugger
  2
  3> **DISCLAIMER**: This is not documentation for the [planned debugger support in Zed](https://github.com/zed-industries/zed/issues/5065).
  4> Rather, it is intended to provide information on how to use an external debugger while developing Zed itself to both Zed employees and external contributors.
  5> Once debugger support is implemented, this section will be updated to provide information on how to use the built-in debugger as part of Zed development.
  6
  7## Build profile considerations
  8
  9By default, builds using the dev and release profiles (release is the profile used for production builds, i.e. nightly, preview, and stable) include limited debug info.
 10
 11This is done by setting the `profile.(release|dev).debug` field in the root `Cargo.toml` field to `"limited"`.
 12
 13The official documentation for the `debug` field can be found [here](https://doc.rust-lang.org/cargo/reference/profiles.html#debug).
 14But the TLDR is that `"limited"` strips type and variable level debug info.
 15
 16In release builds, this is done to reduce the binary size, as type and variable level debug info is not required, and does not impact the usability of generated stack traces.
 17
 18In debug builds, this is done to reduce compilation (especially incremental compilation) time.
 19
 20However, while the type and variable level debug info is not required for good stack traces, it is very important for a good experience using debuggers,
 21as without the type and variable level debug info, the debugger has no way to resolve local variables, inspect them, format them using pretty-printers, etc.
 22
 23Therefore, in order to use a debugger to it's fullest extent, you must compile a new Zed binary, with full debug info.
 24
 25The simplest way to do this, is to use the `--config` flag to override the `debug` field in the root `Cargo.toml` file when running `cargo run` or `cargo build` like so:
 26
 27```sh
 28cargo run --config 'profile.dev.debug="full"'
 29cargo build --config 'profile.dev.debug="full"'
 30```
 31
 32> If you wish to avoid passing the `--config` flag on every invocation of `cargo`. You may also change the section in the [root `Cargo.toml`](https://github.com/zed-industries/zed/blob/main/Cargo.toml)
 33>
 34> from
 35>
 36> ```toml
 37> [profile.dev]
 38> debug = "limited"
 39> ```
 40>
 41> to
 42>
 43> ```toml
 44> [profile.dev]
 45> debug = "full"
 46> ```
 47>
 48> This will ensure all invocations of `cargo run` or `cargo build` will compile with full debug info.
 49>
 50> **WARNING:** Make sure to avoid committing these changes!
 51
 52## GDB/LLDB
 53
 54### Background
 55
 56When installing rust through rustup, (the recommended way to do so when developing Zed, see the documentation for getting started on your platform [here](../development.md))
 57a few additional scripts are installed and put on your path to assist with debugging binaries compiled with rust.
 58
 59These are `rust-gdb` and `rust-lldb` respectively.
 60
 61You can read more information about these scripts and why they are useful [here](https://michaelwoerister.github.io/2015/03/27/rust-xxdb.html) if you are interested.
 62
 63However, the summary is that they are simple shell scripts that wrap the standard `gdb` and `lldb` commands, injecting the relevant commands and flags to enable additional
 64rust-specific features such as pretty-printers and type information.
 65
 66Therefore, in order to use `rust-gdb` or `rust-lldb`, you must have `gdb` or `lldb` installed on your system. If you don't have them installed, you will need to install them in a manner appropriate for your platform.
 67
 68According to the [previously linked article](https://michaelwoerister.github.io/2015/03/27/rust-xxdb.html), "The minimum supported debugger versions are GDB 7.7 and LLDB 310. However, the general rule is: the newer the better." Therefore, it is recommended to install the latest version of `gdb` or `lldb` if possible.
 69
 70> **Note**: `rust-gdb` is not installed by default on Windows, as `gdb` support for windows is not very stable. It is recommended to use `lldb` with `rust-lldb` instead on Windows.
 71
 72If you are unfamiliar with `gdb` or `lldb`, you can learn more about them [here](https://www.gnu.org/software/gdb/) and [here](https://lldb.llvm.org/) respectively.
 73
 74### Usage with Zed
 75
 76#### Running Zed with a Debugger
 77
 78After following the steps above for including full debug info when compiling Zed,
 79You can either run `rust-gdb` or `rust-lldb` on the compiled Zed binary after building it with `cargo build`, by running one of the following commands:
 80
 81```
 82rust-gdb target/debug/zed
 83rust-lldb target/debug/zed
 84```
 85
 86Alternatively, you can attach to a running instance of Zed (such as an instance of Zed started using `cargo run`) by running one of the following commands:
 87
 88```
 89rust-gdb -p <pid>
 90rust-lldb -p <pid>
 91```
 92
 93Where `<pid>` is the process ID of the Zed instance you want to attach to.
 94
 95To get the process ID of a running Zed instance, you can use your systems process management tools such as `Task Manager` on windows or `Activity Monitor` on MacOS.
 96
 97Alternatively, you can run the `ps aux | grep zed` command on MacOS and Linux or `Get-Process | Select-Object Id, ProcessName` in an instance of PowerShell on Windows.
 98
 99#### Debugging Panics and Crashes
100
101Debuggers can be an excellent tool for debugging the cause of panics and crashes in all programs, including Zed.
102
103By default, when a process that `gdb` or `lldb` is attached to hits an exception such as a panic, the debugger will automatically stop at the point of the panic and allow you to inspect the state of the program.
104
105Most likely, the point at which the debugger stops will be deep in the rust standard library panic or exception handling code, so you will need to navigate up the stack trace to find the actual cause of the panic.
106
107This can be accomplished using the `backtrace` command in combination with the `frame select` command in `lldb`, with similar commands available in `gdb`.
108
109Once the program is stopped, you will not be able to continue execution as you can before an exception is hit. However, you can jump around to different stack frames, and inspect the values of variables and expressions
110within each frame, which can be very useful in identifying the root cause of the crash.
111
112You can find additional information on debugging Zed crashes [here](./debugging-crashes.md).