[petsc-users] Tough to reproduce petsctablefind error

[Jed Brown]

It'll be hard to narrow down without a stack trace or reproducer.  I'd
recommend running a small test to ensure that your code is Valgrind
clean before going any further.  Then try to get a stack trace by
running inside a debugger or setting your environment to dump core on
errors.

Chris Hewson <chris at resfrac.com> writes:

> Hi,
>
> I am having a bug that is occurring in PETSC with the return string:
>
> [7]PETSC ERROR: PetscTableFind() line 132 in
> /home/chewson/petsc-3.13.2/include/petscctable.h key 7556 is greater than
> largest key allowed 5693
>
> This is using petsc-3.13.2, compiled and running using mpich with -O3 and
> debugging turned off tuned to the haswell architecture and occurring either
> before or during a KSPBCGS solve/setup or during a MUMPS factorization
> solve (I haven't been able to replicate this issue with the same set of
> instructions etc.).
>
> This is a terrible way to ask a question, I know, and not very helpful from
> your side, but this is what I have from a user's run and can't reproduce on
> my end (either with the optimization compilation or with debugging turned
> on). This happens when the code has run for quite some time and is
> happening somewhat rarely.
>
> More than likely I am using a static variable (code is written in c++) that
> I'm not updating when the matrix size is changing or something silly like
> that, but any help or guidance on this would be appreciated.
>
> *Chris Hewson*
> Senior Reservoir Simulation Engineer
> ResFrac
> +1.587.575.9792