Also worth mentioning: The solution in the patch still leaves a potential problem in the static destruction order, but that's probably safe since it looks like nothing outside SubSystemsManager calls finalize etc. Still, it may be prudent to make more methods private.
-- You received this bug notification because you are a member of DOLFIN Team, which is subscribed to DOLFIN. https://bugs.launchpad.net/bugs/726484 Title: mpi_init is sometimes called on uninitialised object Status in DOLFIN: New Bug description: Due to undefined order of initialisation of static objects, SubSystemsManager::init_mpi is sometimes called before the constructor. The visible effect is (at least in my case) that MPI_Finalize is never called. Patch attached. _______________________________________________ Mailing list: https://launchpad.net/~dolfin Post to : dolfin@lists.launchpad.net Unsubscribe : https://launchpad.net/~dolfin More help : https://help.launchpad.net/ListHelp
