I gave Qwen Code a real native debugger through DAP and MCP

[SLP-DEV1]

I built qwen-dap-mcp, a local DAP → MCP bridge that gives Qwen Code structured access to a real native debugger instead of asking it to infer every crash from source and terminal output alone.

The useful evidence for a native crash is often inside the debugger: stack frames, registers, locals, exception state, disassembly, loaded modules and crash dumps. qwen-dap-mcp exposes that evidence through MCP and keeps the fix/build work in the normal coding-agent workflow.

v0.12.0 adds a compact default agent toolset, while the full low-level debugger surface remains available through QWEN_DAP_MCP_TOOLSET=full. It also includes a reproducible Crash Lab and benchmark scaffold so the workflow can be tested rather than only described.

Current tested path:

CodeLLDB launch/attach through DAP
Windows minidump / postmortem analysis
stack, register, local, module, disassembly and bounded memory evidence
project-frame and fault-operand correlation
bounded runtime root-cause backtracking
diagnose → inspect → fix → build → reproduce → verify orchestration
explicit crash fingerprints and changed-failure detection
local stdio MCP with no arbitrary shell or unrestricted memory-write primitive
Install in Qwen Code:

qwen extensions install SLP-DEV1/qwen-dap-mcp
Or run the published MCP package directly:

npx -y @slp-dev1/qwen-dap-mcp
Repository: https://github.com/SLP-DEV1/qwen-dap-mcp

npm: @slp-dev1/qwen-dap-mcp@0.12.0

Official MCP Registry: io.github.SLP-DEV1/qwen-dap-mcp

I would especially like feedback from people using Qwen Code on native C/C++ projects, and from anyone interested in testing additional DAP adapters.