Bo LorentsenandAnthony
b78f19982f
I really need this for embedded development in IDF and Zephyr, where the chip vendors sometimes provide there own specialized version of the tools, and I need to direct zed to use these. The current GDB adapter only supports the gdb it find in the normal search path, and it also seems like we where not able to transfer gdb specific startup arguments (only `-i=dap` is set) . In order to fix this I (semi wipe using GPT-4.1) expanded the GDB adapter with 2 new config options : * **gdb_path** holds a full path to the gdb executable, for now only full path or relative to cwd * **gdb_args** an array holding additional arguments given to gdb on startup It seemed to me, like the `env` config did not transferred to gdb, so this is added to. I have tested this locally, and it seems to work not only compile :-) Release Notes: debugger: Adds gdb_path and gdb_args to gdb debug adapter options debugger: Fix bug where gdb debug sessions wouldn't inherit the shell environment from Zed --------- Co-authored-by: Anthony <anthony@zed.dev>
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.