[petsc-users] Petsc Fortran Memory stack trace

[Nicholas Arnold-Medabalimi]

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

-- 
Nicholas Arnold-Medabalimi

Ph.D. Candidate
Computational Aeroscience Lab
University of Michigan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20221121/cff59f39/attachment.html>