Other options I have found useful:
-v --leak-check=full --show-reachable=yes
On 11/21/22 11:27 AM, Satish Balay via petsc-users wrote:
valgrind is a useful tool to learn to use..
valgrind --tool=memcheck ./executable
Satish
On Mon, 21 Nov 2022, Nicholas Arnold-Medabalimi wrote:
Hi Petsc users
I'm working on an integration of Petsc into an existing fortran code. Most
of my memory debugging is very primitive and is usually accomplished using
the -check bounds option in the compiler. However with Petsc attached the
stack trace becomes much more opaque compared to the original code. At
least as far as I can tell the error becomes much harder to pin down (just
pointing to libpetsc.so). Any assistance in getting more informative error
messages or checks would be much appreciated.
Sincerely
Nicholas
