On Fri, 17 Sep 2010, Jed Brown wrote: > On Fri, Sep 17, 2010 at 16:35, Tim Kroeger > <[email protected]> wrote: >> Can you (Jed) comment on how it can happen that KSPSolve() prints this error >> message but nicely returns 0? > > CHKERRQ is not being called somewhere in the stack, if it's in PETSc > code, please let me know where it is (or send a full trace). > > As a general rule, always set a breakpoint in PetscError. I have in > my ~/.gdbinit: > > set breakpoint pending on > break PetscError > > Note that -start_in_debugger adds this automatically.
Thank you for this hint. Using this, it was easy to find the point where the macro is not called. It's in libMesh, however, that is in petsc_preconditioner.C, line 49. Actually, in that file, a lot of calls to CHKERRABORT() are missing. Roy, is there any reason for this? If not, I would like to add all these calls. Best Regards, Tim -- Dr. Tim Kroeger CeVis -- Center of Complex Systems and Visualization University of Bremen [email protected] Universitaetsallee 29 [email protected] D-28359 Bremen Phone +49-421-218-7710 Germany Fax +49-421-218-4236 ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
