Skip to content
New issue

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

Strange Error Codes #8

Closed
austinstig opened this issue Feb 26, 2016 · 2 comments
Closed

Strange Error Codes #8

austinstig opened this issue Feb 26, 2016 · 2 comments

Comments

@austinstig
Copy link

I executed the send_receive.rs example. My GCC version is 4.9.2 on a cluster running CentOS 6. My MPICH is 3.1.4. The program seems to produce the correct output except that it is returning strange error codes from Status (see attached). I also tried a few other examples and this behavior happened for them as well. Do you know what might be causing this? My rust-bindgen is using a libclang.so file instead of a libclang.a file but otherwise nothing else seems to be different.

foo.txt

@bsteinb
Copy link
Collaborator

bsteinb commented Feb 26, 2016

Yes, the error field of the status type is simply not filled with any meaningful information by the send and receive type functions. It might be filled with an error code in a situation where you are waiting for the completion of multiple non-blocking point to point operations. This part of MPI is not covered by the bindings yet. (See e.g. MPI_Waitall() on the list of unfinished features in the documentation of the point_to_point module.)

More generally, however, the default behavior of MPI is to abort the program on communication errors rather than returning an error code. The bindings do not change this default at the moment.

I should probably remove the error() getter function and the error field from the Display output of Status.

@austinstig
Copy link
Author

Good to know. Thank you for the information.

@bsteinb bsteinb closed this as completed Feb 26, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants