Add new "console" launch config for cppdbg

[MartinLoeper]

Type: Feature Request

I would like to request a "console" launch config attribute for the cppdbg debugger type similar to #6794.
Is there a reason that the attribute is currently for cppvsdbg only?

[WardenGnaw]

Is there a reason that the attribute is currently for cppvsdbg only?

We never had this support for cppdbg since this would rely on us spawning the terminal. For cppvsdbg we control the terminal launch, in cppdbg, we rely on GDB/LLDB to do so.

See https://github.com/microsoft/MIEngine/blob/de8db64a055ca00d7d38fa4d53b749dd9d493c60/src/MIDebugEngine/Engine.Impl/DebuggedProcess.cs#L786

[MartinLoeper]

Hey @WardenGnaw, thanks for the reply!
Do you think there is currently any way or workaround to make cppdbg use the integrated terminal instead of the debugging console?

[WardenGnaw]

You can force use the integrated terminal if you have externalConsole: false (only on Windows and Linux).

[MartinLoeper]

You meant setting externalConsole: true right?
I think false is already the default.

[seokbeomKim]

@MartinLoeper I'd like to ask about your environment setting. It seems that this thread is quite old..
I've been looking to do the same thing for kernel devleopment attaching gdb + gef. Is there any progress on this? Due to the lack of this feature, I'm considering moving back to vi/emacs since I cannot see disassembler or stack with code at the same time.

[MartinLoeper]

This should actually work fine if you are not using the remote containers extension for vscode. Some extensions have issues with vscode running in a docker container. I think the externalConsole a prime example of a feature that breaks when using a devcontainer. I solved it by using a workaround: gef-remote (run manually using a shell script after starting the debug session) - it is a bit hacky but works

[seokbeomKim]

Thanks for the comment! I should try gef-remote. :)