Debugging MPI Program on M1 #618
Unanswered
Asterix9000
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Well, attaching by program name is not going work in your case, because there's more than one instance of that program running. How would the debugger know which one you wanted to debug? Try removing the "program" attribute from launch configuration. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am currently in the process of setting up my vscode debugging environment for debugging an MPI project on my new M1 macbook. I have spent several days trying to get this setup and am at a bit of a loss as to how to proceed. Any help would be much appreciated.
Describe the bug
I started setting everything up by following these two tutorials:
https://iamsorush.com/posts/debug-mpi-vs-code/
https://medium.com/@li.nguyen_15905/setting-up-vscode-for-mpi-programming-b6665da6b4ad
I installed the CodeLLDB extension per the suggestion in:
microsoft/vscode-cpptools#6779
I also referred to this thread as I was trying to set everything up:
microsoft/vscode-cpptools#1723
After starting the MPI program I attempt to attach the debugger to one of the processes, which yields the following error:
To Reproduce
Here is a simple reproducer program, along with corresponding CMakeLists.txt, build script, launch.json, tasks.json, and c_cpp_properties.json . To reproduce the issue copy the .json files, install the CodeLLDB extension, build the reproducer, then run it with mpirun -np 4 ./test.exe ( not sure if this issue is specific to M1 yet ). Note that this requires a working version of MPI, which I installed using homebrew.
Simple reproducer:
CMakeLists.txt:
build script:
launch.json:
task.json:
c_cpp_properties.json:
Beta Was this translation helpful? Give feedback.
All reactions