Hi Lawrence, Thanks for the guidance. You'll find the output attached. Floriane ________________________________ De : firedrake-bounces@imperial.ac.uk <firedrake-bounces@imperial.ac.uk> de la part de Lawrence Mitchell <lawrence.mitchell@imperial.ac.uk> Envoyé : jeudi 8 février 2018 11:06 À : firedrake@imperial.ac.uk Objet : Re: [firedrake] .at() PETSC error On 08/02/18 10:57, Floriane Gidel [RPG] wrote:
Dear Lawrence,
Thanks. The firedrake status on the remote machine is:
OK, so the only differences are in firedrake itself (and those changes only update the documentation). To find out what's going on, we'll need to see a C level backtrace. Can you please run: $ gdb --args python TOC2.py This will start python running in a C debugger. You should see something like: ... For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from python...(no debugging symbols found)...done. (gdb) The "(gdb) " line is a prompt. We want to stop when we hit this error, so type: (gdb) break PetscError Function "PetscError" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (PetscError) pending. Say "y" to the prompt. Now we run the program: (gdb) run Eventually you will hit an error (I can't show you this because I don't see it!). At that point type: (gdb) backtrace full And please paste all the output. This will allow us to see where this out of bounds memory access is coming from (hopefully!) Cheers, Lawrence _______________________________________________ firedrake mailing list firedrake@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/firedrake