When processes get stuck, you can attach gdb to one process and back trace its
call stack to see what it is doing, so we can have better understanding.
--Junchao Zhang
On Fri, Sep 13, 2019 at 11:31 AM José Lorenzo via petsc-users
mailto:petsc-users@mcs.anl.gov>> wrote:
Hello,
I am solving a f
> On Sep 13, 2019, at 11:37 PM, José Lorenzo via petsc-users
> wrote:
>
> I'm using PETSc 3.10.2, I guess it is the master branch but I do not know for
> sure as I didn't install it myself.
>
> You are right, each processor provides data for all the boundary entries.
>
> I have carried out
What version of PETSc is this? The master branch?
> call VecSetValues(H, nedge_all, edgappglo(diredg_app) - 1, Hself, ADD_VALUES,
> ierr)
So each process is providing all data for all the boundary entries in the
vector?
I don't think there is anything wrong with what you are doing but the
