On Mon, Nov 30, 2015 at 7:59 AM, Soumya Mukherjee <soumyamechan...@gmail.com
> wrote:
> It is a PETSc error. And I just wanted to know if runs without an error in
> your machine.
>
This is not a PETSc error, as such. PETSc installs a signal handler so that
we can try and get more
information about signals. However, it is likely that you have a Floating
Point Exception, like a divide
by zero, in your user code.
Thanks,
Matt
> On Nov 30, 2015 4:34 AM, "Jose E. Roman" <jro...@dsic.upv.es> wrote:
> >
> > I am not going to run your code. We are not a free debugging service.
> You have to debug the code yourself, and let us know only if the issue is
> related to the SLEPc library. Start adding error checking code with the
> CHKERRQ macro to all PETSc/SLEPc calls. This will catch most errors. It no
> errors are detected, then run with a debugger such as gdb or valgrind to
> determine the exact point where the program fails.
> >
> > Jose
> >
>
--
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
