Simon Sobisch

One thing highlighted in #290: extended-remote may want to attach to a running process on the server. So far the only way to do this is to use autorun commands....

Seems to only happen when ssh to Windows... here are the same scenarios with ssh to WSL: scenario 1: ~~~ -gdb-exit GDB -> App: {"outOfBandRecord":[],"resultRecords":{"resultClass":"exit","results":[]}} GDB -> App: {"outOfBandRecord":[{"isStream":false,"type":"notify","asyncClass":"thread-exited","output":[["id","1"],["group-id","i1"]]}]} GDB...

> Or is there a way to use a .gdbinit file as a workaround? Yes, if your setup uses a .gdbinit file (depend on the GDB configuration, commonly "in the...

Yes, that sounds like the correct approach. Do you mind adding an example? A good case would actually be #326 - the code on the extension side is technically the...

While it is possible to import `vscode` - using it breaks the backend. When this is done we could easily use an output pane via: ```ts import { OutputChannel, window...

Actually a follow-up to #217.

What is the state of this PR? Is it a draft? Is it abandoned?

It's been a while... I'd like to take that up on current master (ideally after #323 and #316 were merged as those change the initialization): * adding the `initializeToDefault()` -...

Seems like there is no way back in the dap - so it would mean to do the necessary communication first.

The frontend code would be along: ```ts import * as vscode from "vscode"; if (record.asyncClass == "breakpoint-added" || record.asyncClass == "breakpoint-modified" || "breakpoint-deleted") { var file = parsed.record("fullname"); var line...