On Wed, May 18, 2016 at 3:04 PM, Jed Brown <j...@jedbrown.org> wrote:
> John Peterson <jwpeter...@gmail.com> writes: > > It would be nice if all versions of libmesh worked with debug-enabled > > PETSc, but that's not something that gets tested very often... > > *tears* > > I'd like to know what is causing this SEGV. It shouldn't happen unless > some side-effects are being abused, and even then, debug mode should > give a better error message instead of waiting for SEGV. > OK, if Kathrin still has debug builds sitting around, she may be able to get a stack trace by running the example in question with: libtool --mode=execute gdb ./example-dbg refinement_type=matchedhp max_r_steps=5 and then type "r" to run the program. It should stop when it segfaults, and then you can type "bt" to get a backtrace. I'll also see if I can reproduce on a 3.5.x debug PETSc build... -- 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
