Hello,
since our application has two possible entry paths, petsc could be initialized
at different positions. When used as a library (in contrast to a standalone
executable), the code looks like:
PetscErrorCode ierr;
std::cout Petsc before PetscInitializeNoArguments() std::endl;
On Mon, Dec 15, 2014 at 7:12 AM, Florian Lindner mailingli...@xgm.de
wrote:
Hello,
since our application has two possible entry paths, petsc could be
initialized at different positions. When used as a library (in contrast to
a standalone executable), the code looks like:
PetscErrorCode
Are you setting PETSC_COMM_WORLD before these calls? Perhaps on some
processes but not on others?
Barry
On Dec 15, 2014, at 7:52 AM, Matthew Knepley knep...@gmail.com wrote:
On Mon, Dec 15, 2014 at 7:12 AM, Florian Lindner mailingli...@xgm.de wrote:
Hello,
since our application
