microsoft / microsoft/vscode

Hide GDB/MI commands (-exec) in VS Code Debug Console

Open
#335,616 0 comments 0 reactions 1 assignee Claimed by @bryanchen-d View on GitHub
triage-needed
Dominant language
TypeScript
Stars
193k
Forks
42.4k
PR merge metrics
PR metrics pending

Description

When using the C/C++ extension with GDB (cppdbg + GDB/MI), the Debug Console exposes internal GDB/MI commands:

-exec-next
-exec-step
-exec-continue

instead of normal debugger commands:

next
step
continue

These are implementation details of the GDB/MI protocol and should not be visible in the user-facing interface.

A debugger interface should abstract the underlying implementation and provide a consistent user experience regardless of whether the backend is GDB, LLDB, or another debugger.

Please consider adding an option to hide MI commands in the Debug Console, for example:

"debug.console.showMICommands": false

while keeping raw MI output available for developers who need protocol-level debugging.

This would improve usability and better follow interface abstraction principles.

Thank you.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.