Simon Sobisch

That's not possible because the debug console is for the debugger; what _would_ be possible though is to create a pseudo-terminal which would have _only_ the program (and because of...

Thanks for the possibility to go with option 1. Note. that is _not_ about custom packages, but effectively to run-time toggle the option used in `MI2.sendRaw()` (only place where `printCalls`...

I now see what you've meant. For this issue and other's we need a communication between frontend and backend. I'm creating a new issue for that.

Just rechecked for the Vim TermDebug plugin which used both "to ensure everything is fine" - `set mi-async` is a GDB 7.8 feature (Released Jul 2014), which also comes with...

So some months passed. I'd actually suggest to: * implement `autorunBefore` from #99 * in the new default use `gdb-set mi-async` (users with old GDB version can adjust this)

Nice idea. But those preload skripts are actual skripts loaded in the actual debugger aren't they? While that would be useful to have automated I can (and actually do) this...

@mohamedchebbii I'm very interested in this, can you please take that up again from current master with plain ssh2? The way to do the hoping is now explicit documented at...

see also #242 (so far that's a separate view, but we should provide those as variables)

That looks like a neat idea. Checking the discussion within multiple vscode extensions the separate register panel was "dropped"; instead the "way to go" is using the Variable panel. For...

> It should be possible to do a more reliable fix by inspecting the current state of GDB somehow. `-thread-info` should be possible to get the state, if it says...