Skip to content

Troubleshooting

Sven Scharmentke edited this page Oct 11, 2025 · 4 revisions

Troubleshooting

Installation Issues

CDB Not Found

Error: CDB executable not found

Solutions:

  1. Check if CDB is in PATH: where cdb
  2. Install Windows SDK with "Debugging Tools for Windows"
  3. Set custom path in mcp.json:
    "args": ["-m", "mcp_windbg", "--cdb-path", "C:\\Program Files (x86)\\Windows Kits\\10\\Debuggers\\x64\\cdb.exe"]

Python Module Not Found

Error: No module named 'mcp_windbg'

Solutions:

  1. Verify: pip list | findstr mcp-windbg
  2. Reinstall: pip uninstall mcp-windbg && pip install mcp-windbg
  3. Use full Python path in mcp.json for virtual environments:
    "command": "${workspaceFolder}/.venv/Scripts/python"

Configuration Issues

VS Code MCP Not Working

Problem: Tools don't appear in Copilot

Solutions:

  1. Enable MCP in Copilot settings (Ctrl+, → search "MCP")
  2. Verify .vscode/mcp.json exists and has valid JSON
  3. Restart VS Code completely
  4. Check Output → Model Context Protocol for errors

Symbol Loading Issues

Problem: "No symbols" or symbol loading fails

Solutions:

  1. Configure symbol path in mcp.json:
    "env": {"_NT_SYMBOL_PATH": "SRV*C:\\Symbols*https://msdl.microsoft.com/download/symbols"}
  2. Test: python -m mcp_windbg --symbols-path "SRV*C:\Symbols*https://msdl.microsoft.com/download/symbols"
  3. Check network access to https://msdl.microsoft.com

Runtime Issues

Command Timeouts

Problem: "Command timeout" errors

Solutions:

  1. Increase timeout: "args": ["-m", "mcp_windbg", "--timeout", "120"]
  2. Use simpler commands first
  3. Avoid broad analysis on large dumps

Memory Issues

Problem: Out of memory or slow performance

Solutions:

  1. Close unused sessions: "Close the crash dump session for C:\dumps\large.dmp"
  2. Analyze specific areas instead of full dumps
  3. Use 64-bit CDB for large dumps

File Access Issues

Problem: "Access denied" or "File not found"

Solutions:

  1. Check file permissions and use absolute paths
  2. Run VS Code as administrator if needed
  3. Copy network files locally for analysis

Remote Debugging Issues

Connection Failures

Problem: Cannot connect to remote target

Solutions:

  1. Use correct format: tcp:Port=5005,Server=192.168.0.100
  2. Test connectivity: telnet 192.168.0.100 5005
  3. Check target firewall and debugging settings

Common Error Messages

Error Solution
"Failed to load dump file" Check file integrity and permissions
"Symbol loading failed" Verify symbol path and network connectivity
"Remote connection refused" Check port and firewall settings
"Command not recognized" Verify WinDbg command syntax

Diagnostics

Enable Verbose Logging

"args": ["-m", "mcp_windbg", "--verbose"]

Test Components

# Check versions
python --version
cdb -version

# Test installation  
pip list | findstr mcp-windbg
python -m mcp_windbg --help

# Test connectivity
curl -I https://msdl.microsoft.com/download/symbols

Getting Help

  1. Check VS Code Output → Model Context Protocol
  2. Enable verbose logging
  3. Search GitHub Issues
  4. Create new issue with:
    • OS, Python, VS Code versions
    • Complete error messages
    • Steps to reproduce
    • Configuration files

Clone this wiki locally