Andrew Davis <[email protected]> writes:
> This does look like some kind of MPI issue. Just to be safe I tried
> reinstalling MPI and then reconfigure/compiling PETSc and libMesh.
Exactly which options are you configuring with? This message makes it
sound like you have an MPI-enabled PETSc and a libMesh configured
without MPI.
> This resulted in the same runtime error (the stack trace) as before.
Which one? In MPI_Attr_get? Can you attach a debugger and find out
what out what the value of comm was? MPIUNI's implementation is simple:
int MPI_Attr_get(MPI_Comm comm,int keyval,void *attribute_val,int *flag)
{
if (comm-1 < 0 || comm-1 > 3) return 1;
if (!keyval) Keyval_setup();
*flag = attr[comm-1][keyval].active;
*(void**)attribute_val = attr[comm-1][keyval].attribute_val;
return MPI_SUCCESS;
}
It appears that libMesh::COMM_WORLD is being set to 0 when not using
MPI?
------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users
