Re: [petsc-dev] VS Code debugger and PETSc

I don't have. I think the main problem with petsc is one usually needs to debug with multiple MPI ranks. For light debug, I use gdb or tmpi ; for heavy debug, I use ddt on servers (need license). --Junchao Zhang On Fri, May 28, 2021 at 3:14 PM Aagaard, Brad

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

And valgrind sees this. I think the jump to the function is going to the wrong place. I'm giving up on PGI but can try newer versions of GCC. (what is the deal with the range of major releases, 4-10?) (as I said this looks like an error that a user is getting so I'd like to figure it out). 0

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

On Sat, May 29, 2021 at 11:46 PM Junchao Zhang wrote: > try gcc/6.4.0 > 6.4.0 is the default and what I've been using. 6.4.0 builds and it has worked but I am now getting this segv (valgrind trace below) in adams/landau-mass-opt. My thinking is to try other versions. > --Junchao Zhang > > >

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

Try without Valgrind, put a CHKMEMQ; just before the call to LandauKokkosJacobian and as its first line. And run with -malloc_debug. This is a less optimal way to find memory corruption but may be more useful in this case. > On May 29, 2021, at 10:46 PM, Junchao Zhang wrote: > > try

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

try gcc/6.4.0 --Junchao Zhang On Sat, May 29, 2021 at 9:50 PM Mark Adams wrote: > And I grief using gcc-8.1.1 and get this error: > > /autofs/nccs-svm1_sw/summit/gcc/8.1.1/include/c++/8.1.1/type_traits(347): > error: identifier "__ieee128" is undefined > > Any ideas? > > On Sat, May 29, 2021

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

On Sun, May 30, 2021 at 12:08 AM Barry Smith wrote: > >Try without Valgrind, put a CHKMEMQ; just before the call to > LandauKokkosJacobian and as its first line. And run with -malloc_debug. > This is a less optimal way to find memory corruption but may be more useful > in this case. > I

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

And I grief using gcc-8.1.1 and get this error: /autofs/nccs-svm1_sw/summit/gcc/8.1.1/include/c++/8.1.1/type_traits(347): error: identifier "__ieee128" is undefined Any ideas? On Sat, May 29, 2021 at 10:39 PM Mark Adams wrote: > And valgrind sees this. I think the jump to the function is