On Wed, May 18, 2016 at 3:40 PM, Kathrin Smetana <ksmet...@mit.edu> wrote:
> Hi, > > Unfortunately I deleted the debug build in the meantime. > I built PETSc 3.5.3 using the same configure flags you mentioned (other than --with-dynamic-loading and --download-umfpack=1, which did not seem to be valid), and I could not reproduce the segfault in adaptivity_ex3. The inconsistent behavior you were seeing between opt and dbg modes make me suspect something wrong with either the PETSc or libmesh builds, or both. One unlikely possibility: did you definitely use the same C++ compiler to build both PETSc (since you pass --with-clanguage=cxx) and libmesh? libmesh will pick up mpicxx automatically from your environment, whereas I think PETSc may use $CXX by default (?). If those two things were somehow pointing to different compilers, you could have an issue. -- John ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
