Re: [petsc-dev] [petsc-users] strange segv

Oh right. I had forgotten about cuda-memcheck. Thanks for reminding me. It has never saved me, yet, so it has not been etched in my brain like valgrind :) On Sun, May 30, 2021 at 11:53 AM Jacob Faibussowitsch wrote: > The problem was that I was accessing a device pointer on the host. > > Maybe t

Re: [petsc-dev] [petsc-users] strange segv

Jacob, Great suggestion. https://gitlab.com/petsc/petsc/-/merge_requests/4050 > On May 30, 2021, at 10:53 AM, Jacob Faibussowitsch > wrote: > >> The problem was that I was accessing a device pointer on the host. >> >> Maybe the

Re: [petsc-dev] [petsc-users] strange segv

> The problem was that I was accessing a device pointer on the host. > > Maybe the fact that valgrind did not print a source code line (it was in host > code) is a hint that you are accessing a device pointer? > > ==77820== Invalid read of size 4 > ==77820==at 0x7E69068: LandauKokkosJacobian

Re: [petsc-dev] [petsc-users] strange segv

The problem was that I was accessing a device pointer on the host. Maybe the fact that valgrind did not print a source code line (it was in host code) is a hint that you are accessing a device pointer? ==77820== Invalid read of size 4 ==77820==at 0x7E69068: LandauKokkosJacobian (in /gpfs/alpi