The problem is that the handler of yours causes execution of some class destructors of my code, which I do not want to happen. This happens if I build my code in DEBUG mode when I do not want any exception catching.
I'm not sure why this happens. Solution of Paul helped me. Michael. On 08/26/2015 05:06 PM, John Peterson wrote: > > > On Tue, Aug 25, 2015 at 11:29 AM, Michael Povolotskyi > <mpovo...@purdue.edu <mailto:mpovo...@purdue.edu>> wrote: > > Dear Libmesh developers, > recently I saw a problem with libmesh_terminate_handler > > <http://libmesh.github.io/doxygen/namespacelibMesh.html#ac42cc9a668f69fbf3514c2585986dcbe>() > Somehow it conflicts with my code when an exception in my code (not in > libmesh) is generated. > So, I need to disable the catch of exceptions inside the libMesh. > Is the only way to do so is to not define LIBMESH_ENABLE_EXCEPTIONS? > How this can be done during configuration? > > > Did Paul's response fix the issue for you? > > Even though disabling exceptions in libmesh might work around the > problem, I'd still like to know a bit more about what "conflicts with > my code" means? Are you declaring your own terminate handler > with std::set_terminate and libmesh's gets in the way? > > Generally speaking, we'd like to be good exception handling citizens, > so I'd like to know if there's something we can improve here... > > -- > John -- Michael Povolotskyi, PhD Research Assistant Professor Network for Computational Nanotechnology Hall for Discover and Learning Research, Room 441 West Lafayette, IN 47907 Phone (765) 4949396 ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
