This just sounds like a bug. Valgrind would be great and a stack trace would be great also. (compile with -g to get source lines). If you just get a segv then a debugger should stop there. If you are getting a PETSc error message then put a breakpoint in PetscError. Mark
On Fri, Nov 6, 2020 at 4:45 AM Stefano Zampini <[email protected]> wrote: > Enrico, > > some more information would be helpful, like a full petsc error message. > Also, PETSc version and configuration would be great. > Can you run valgrind to detect where and why the code is erroring? or run > with -on_error_attach_debugger ? > > Thanks > Stefano >
