Denis Davydov

@fghoussen here's the update 1. having `external debug_init` in `pdgetv0.f` ``` include 'debug.h' include 'stat.h' external debug_init ``` does not help, i still get to the printing 2. while adding...

> Your last chance could be Unfortunately that does not change the behaviour 😞 . But thanks for the suggestion, @fghoussen

> What is the compiler you use ? Is it intel (sometimes bugged) ? Did you try with gnu ? gnu 4.8.5. > Did you try: will do on Monday...

@pieandcakes that's unfortunate, but thanks for the prompt and detailed comment, though 👍 EDIT: i guess the only way to hack this is separate _attach_ configs: ``` { "name": "(lldb)...

> Once you have started debugging, you can't really debug again. I see, thanks for clarifying.

@pieandcakes I was said upstream that the support for multiple processes is already there: > The VS Code debugger supports multiple processes. See https://code.visualstudio.com/updates/v1_20#_node-debugging. The animated gif shows VS Code...

based on the discussion in `vscode` issue, I would say one needs to do two things: 1. from `cpptools` debugger configuration, run a given executable with `mpirun -np X my_executable`...

@pieandcakes sure, here's a simple example ``` // compile with: // mpic++ -std=c++11 mpi_example.cc -o mpi_example // run with: // mpirun -np 2 mpi_example // debug manually with different terminals...

@WardenGnaw thanks entertaining the idea, appreciate it. > this is enough work that we would need to see significant interest in using this from the MPI community before we would...

pinging @KyleDavisSA and @uekerman