[petsc-users] DMForestTransferVec with -petscspace_order 0

[Tobin Isaac]

Hi Yann,

Thanks for pointing this out to us.  Matt and I are the two most
actively developing in this area.  We have been working on separate
threads and this looks like an issue where we need to sync up.  I
think there is a simple fix, but it would be helpful to know which
version petsc you're working from: I'm seeing different
behavior.  Could you please send along more complete output?

Cheers,
  Toby

On Mon, Apr 02, 2018 at 04:42:29PM +0200, yann JOBIC wrote:
> Hi,
> 
> I'm using DMForestTransferVec, as in "dm/impls/forest/examples/tests/ex2.c".
> 
> I would like to use it with a space approximation order at zero
> (-petscspace_order 0). However, in this case, it's not working (valgrind
> output of ex2.c from forest test) :
> 
> ==8604== Conditional jump or move depends on uninitialised value(s)
> ==8604==    at 0x47D74F: DMPlexVecGetClosure (plex.c:4035)
> ==8604==    by 0x557612: DMPlexLocatePoint_General_3D_Internal
> (plexgeometry.c:153)
> ==8604==    by 0x559B85: DMPlexLocatePoint_Internal (plexgeometry.c:383)
> ==8604==    by 0x611EED: DMPlexComputeInjectorReferenceTree
> (plextree.c:3247)
> ==8604==    by 0x6148DB: DMPlexReferenceTreeGetInjector (plextree.c:3454)
> ==8604==    by 0x61EAD8: DMPlexTransferVecTree_Inject (plextree.c:4319)
> ==8604==    by 0x620CC1: DMPlexTransferVecTree (plextree.c:4527)
> ==8604==    by 0x7F23D8: DMForestTransferVec_p8est (pforest.c:4239)
> ==8604==    by 0x429B48: DMForestTransferVec (forest.c:985)
> ==8604==    by 0x40BB8A: main (transf_test.c:136)
> 
> With the error message :
> 
> [0]PETSC ERROR: Caught signal number 11 SEGV: Segmentation Violation,
> probably memory access out of range
> 
> It's working fine in 2D (p4est). The problem arise in 3D (p8est).
> 
> Is it an expected behavior ? Am i doing something wrong ?
> 
> Thanks in advance,
> 
> Yann
>