Hi, On Mon, 2021-01-25 at 15:05 +0100, Thomas Koenig via Gcc wrote: > $ valgrind --version > valgrind-3.15.0 > $ gfortran -g hello.f90 > $ valgrind ./a.out > [...] > --4184-- WARNING: Serious error when reading debug info > --4184-- When reading debug info from > /home/ig25/lib64/libgfortran.so.5.0.0: > --4184-- Ignoring non-Dwarf2/3/4 block in .debug_info > --4184-- WARNING: Serious error when reading debug info > --4184-- When reading debug info from > /home/ig25/lib64/libgfortran.so.5.0.0: > > [...] > > --4184-- WARNING: Serious error when reading debug info > --4184-- When reading debug info from /home/ig25/lib64/libgcc_s.so.1: > --4184-- Ignoring non-Dwarf2/3/4 block in .debug_info > > > [...] > > --4184-- WARNING: Serious error when reading debug info > --4184-- When reading debug info from > /home/ig25/lib64/libquadmath.so.0.0.0: > --4184-- Ignoring non-Dwarf2/3/4 block in .debug_info > > So, the problem (at least for me) is that libgfortran and > other libraries are built in a format that valgrind can not > understand, so it becomes much harder to debug libgfortran :-(
I have a patch for that: https://code.wildebeest.org/git/user/mjw/valgrind/commit/?h=dwarf5 It needs a little bit more cleanup, but should already work as expected. Cheers, Mark
