Randall,
I have resolved in the problem in branch barry/fortran-initialize-objects
(now in next for testing) which defaults to initializing the PETSc objects in
Fortran and removes the use of PetscObjects in Fortran common blocks to prevent
compile errors. Soon will be in master
Barry
Sorry this is actually in master already
> On Jan 18, 2018, at 5:00 PM, Smith, Barry F. wrote:
>
>
> This is a known issue without a perfect solution.
>
> The problem is that by default PETSc fortran types, like type(tKSP) are not
> initialized but we want to check if they are a s
This is a known issue without a perfect solution.
The problem is that by default PETSc fortran types, like type(tKSP) are not
initialized but we want to check if they are a special null character, for
example PETSC_NULL_KSP. So we could initialize them but then they cannot be
used in
The very simple attached program throws lots of valgrind errors.I am using pets 3.8.3, compiled with the following options: ./configure \ --with-debugging=1 \ --with-fortran=1 \ --download-mpich=../mpich-3.3a2.tar.gz \ The makefile, run file, and valgrind output are also attached.Randy M.
cmd_t
