You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I have gdb setup to print out the info I want, and basically just want a fullscreen console that gets its breakpoints set from vscode. I can't use the external terminal as described in issue #76.
Was wondering if it would be possible to ask for an option in the launch config where you set the extension to only provide the gdb output? Would this be something hard to accomplish? Preferably I'd like to keep working in the integrated console.
Example of what I have and what I want
The text was updated successfully, but these errors were encountered:
If this is added then GDB would need to be started in either the integrated or an external terminal - but within a shell, as you have a bunch of terminal escape sequences in here.
I think that would be possible as you can use a similar setup in Vim's Termdebug, which also integrates debugging via mi, as is done in this extension. Effectively this would mean 1 application terminal (either integrated or external), 1 debugging console as it is now and 1 gdb tty in another integrated/external terminal.
Do you mean it would pop up as an integrated terminal, like a task? I'd be fine with that.
My use case is that I want the nice functionality of starting the gdb session the extension provides, but then I want to mainly work with the gdb session through a terminal.
Hi! I have gdb setup to print out the info I want, and basically just want a fullscreen console that gets its breakpoints set from vscode. I can't use the external terminal as described in issue #76.
Was wondering if it would be possible to ask for an option in the launch config where you set the extension to only provide the gdb output? Would this be something hard to accomplish? Preferably I'd like to keep working in the integrated console.
Example of what I have and what I want
The text was updated successfully, but these errors were encountered: