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. Jed ------------------------------------------------------------------------------ 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
