Pierson Lee

>One would, of course, need to manually switch between debuggers for each process in the GUI but this should be fine for up to 4-8 processes, which is often enough...

@davydden Even then, you can only attach one process at a time so it won't get you too far. Once you have started debugging, you can't really debug again.

@davydden we can take that as a suggested feature request. Can you provide a project with a repro? I don't have experience with mpirun.

@csholmq I think you need to start with the C++ Launch scenario to do remote GDB. Can you recreate your `launch.json` using that section and see if it works for...

@csholmq - You can enable logging through the logging tag in `launch.json`. I would look at either `trace\traceResponse` or `engineLogging`. The `engineLogging` are the MICommands we send to the debugger...

@paulmaybee @jacdavis Can either of you provide any insight?

@csholmq You want to use the `"request": "launch"` option within the launch.json with the `miDebuggerServerAddress` and `miDebuggerPath` options. The dimming is something that VSCode does and I think it means...

@therealkenc we have added the ability for `pipeTransport` with the `0.10.0` update. You can read more about it [here](../wiki/PipeTransport). This should allow you do the remote debugging with SSH using...

@csholmq Those unwanted commands are part of the `MIEngine` setup. You can see the code [here](https://github.com/Microsoft/MIEngine/blob/master/src/MIDebugEngine/Engine.Impl/DebuggedProcess.cs#L483) is where the `target-async` is fired. When we launch, we break at the first...

@nilanjan I'll add it to the backlog but in the meantime you can use the gdb-mi [command](http://www.sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Variable-Objects.html): `-var-set-format` in the debugConsole by typing `-exec -var-set-format `. The difficulty we have...