Document macOS developer mode for Rust debugging in VS Code - #1779
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Copilot review overview
🔵 Needs a closer look
Final human review is warranted for the macOS debugging guidance.
Review effort: Lite
Findings: None
What changed in this PR
Documents the macOS developer-tools prerequisite for attaching CodeLLDB to Aspire-managed Rust processes in VS Code.
Changes:
- Adds
DevToolsSecuritystatus and enable commands. - Clarifies administrator authentication and distinction from iOS Developer Mode.
- Links to CodeLLDB and limits the guidance to this prerequisite.
| File | Description |
|---|---|
src/frontend/src/content/docs/integrations/frameworks/rust/rust-host.mdx |
Adds macOS VS Code debugging guidance. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Sébastien Ros (@sebastienros) should this be targeting |
Frontend HTML artifact readyThe latest frontend build uploaded the This comment updates automatically when a new frontend build artifact is uploaded. |
|
David Pine (@IEvangelist) we are shipping Rust debugger support in 13.6. |
Summary
Document the macOS developer tools access prerequisite when attaching CodeLLDB in VS Code to a Cargo/Rust process started by Aspire. Include the exact status and enable commands, administrator authentication requirement, and distinction from iOS device Developer Mode. This was observed when CodeLLDB attach failed with developer mode disabled and breakpoints/stepping worked after the user enabled it; the guidance does not claim to resolve all attach failures.
Third-party links and affiliations
Added a link to the CodeLLDB VS Code Marketplace listing. No material affiliation.
Validation
git diff --checkpassed. Verifiedaspire runagainst the existing Aspire CLI command reference. Documentation-only change; no dependencies or application code changed.