Hello,
I quote from the SUSv3:
Many functions provide an error number in errno, which has type int and is
defined in . The value of errno shall be defined only after a
call to a function for which it is explicitly stated to be set and until
it is changed by the next function call or if the applic
Yup, it does. There's nothing in the standard that says it isn't
allowed to. Given the number of system/libc calls involved in doing
communication, pretty much every MPI function is going to change the
value of errno. If you expect otherwise, I'd modify your
application. Most cluster-ba
I am trying to experiment with openmpi and following trivial code
(although runs) affects value of errno
#include
#include
int main(int argc, char** argv)
{
int _procid, _np;
std::cout << "errno=\t" << errno << std::endl;
MPI_Init(&argc, &argv);
std::cout << "errno=\t" << e
