We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
May relate to #8.
The text was updated successfully, but these errors were encountered:
Managed to attached VS to the rank 0 and if this does not modify the behavior, this appears to be stuck in an unsafe operation MPI_Alltoall.
MPI_Alltoall
MPI.dll!MPI.Intercommunicator.Alltoall<int>(int[] inValues, ref int[] outValues) Line 721 C# MPI.dll!MPI.Intercommunicator.Alltoall<int>(int[] values) Line 633 C# > IntercommunicatorTest.exe!IntercommunicatorTest.IntercommunicatorTest.DoTest(string[] args) Line 403 C# TestCommons.dll!MPI.TestCommons.MPIDebug.Execute(System.Action<string[]> doTest, string[] args) Line 83 C# IntercommunicatorTest.exe!IntercommunicatorTest.IntercommunicatorTest.Main(string[] args) Line 24 C#
unsafe { errorCode = Unsafe.MPI_Alltoall(Marshal.UnsafeAddrOfPinnedArrayElement(inValues, 0), 1, datatype, Marshal.UnsafeAddrOfPinnedArrayElement(outValues, 0), 1, datatype, comm); }
not sure where to go from this point.
I note that there may be a minor version of MSMPI up from the one (10.0) that I used to diagnose. Worth upgrading/testing?
Sorry, something went wrong.
Tidy ups to upgrade to netstandard2 or target FW 4.7.2. Diagnosing is…
f4f18a4
…sue #12
No branches or pull requests
May relate to #8.
The text was updated successfully, but these errors were encountered: