* Re: Non-dwarf blocks detected by valgrind [not found] ` <362769a6-4184-e59b-ded1-7cbe972c84ba@codesourcery.com> @ 2021-01-25 14:05 ` Thomas Koenig 2021-01-25 14:38 ` Mark Wielaard 2021-01-25 14:40 ` Tobias Burnus 0 siblings, 2 replies; 5+ messages in thread From: Thomas Koenig @ 2021-01-25 14:05 UTC (permalink / raw) To: Tobias Burnus, Paul Richard Thomas; +Cc: fortran, gcc mailing list Hi Tobias, >> Does this constitute a regression? > > From your description, yes. Can you give more details how to reproduce it? $ cat hello.f90 print *,"Hello, world!" end $ 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 :-( Is there a way to configure the build so that the old debug format is used for the libraries? Best regards Thomas ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Non-dwarf blocks detected by valgrind 2021-01-25 14:05 ` Non-dwarf blocks detected by valgrind Thomas Koenig @ 2021-01-25 14:38 ` Mark Wielaard 2021-01-25 17:08 ` Mark Wielaard 2021-01-25 14:40 ` Tobias Burnus 1 sibling, 1 reply; 5+ messages in thread From: Mark Wielaard @ 2021-01-25 14:38 UTC (permalink / raw) To: Thomas Koenig, Tobias Burnus, Paul Richard Thomas Cc: gcc mailing list, fortran 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 ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Non-dwarf blocks detected by valgrind 2021-01-25 14:38 ` Mark Wielaard @ 2021-01-25 17:08 ` Mark Wielaard 0 siblings, 0 replies; 5+ messages in thread From: Mark Wielaard @ 2021-01-25 17:08 UTC (permalink / raw) To: Thomas Koenig, Tobias Burnus, Paul Richard Thomas Cc: gcc mailing list, fortran On Mon, 2021-01-25 at 15:38 +0100, Mark Wielaard wrote: > On Mon, 2021-01-25 at 15:05 +0100, Thomas Koenig via Gcc wrote: > > --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. Cleaned up and submitted upstream: https://bugs.kde.org/show_bug.cgi?id=432102 Also backported to Fedora 34 valgrind package: https://bodhi.fedoraproject.org/updates/FEDORA-2021-6335fad95d Cheers, Mark ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Non-dwarf blocks detected by valgrind 2021-01-25 14:05 ` Non-dwarf blocks detected by valgrind Thomas Koenig 2021-01-25 14:38 ` Mark Wielaard @ 2021-01-25 14:40 ` Tobias Burnus 2021-01-25 14:55 ` Thomas Koenig 1 sibling, 1 reply; 5+ messages in thread From: Tobias Burnus @ 2021-01-25 14:40 UTC (permalink / raw) To: Thomas Koenig, Paul Richard Thomas; +Cc: gcc mailing list, fortran Hi Thomas, which binutil version do you have? I am asking because Jakub just submitted: https://gcc.gnu.org/pipermail/gcc-patches/2021-January/564206.html If that does not help, it might be that valgrind simply does not like the DWARF which GCC now produces by default. Defaulting to 4: Well, one way would be to use '4' in "init(5)" of "gdwarf-" in gcc/common.opt. Tobias PS: When checking myself, I did not set LD_LIBRARY_PATH, using the *.so of the Linux distro; hence, I might have missed the issue you are seeing. On 25.01.21 15:05, Thomas Koenig via Fortran wrote: > > Hi Tobias, > >>> Does this constitute a regression? >> >> From your description, yes. Can you give more details how to >> reproduce it? > > $ cat hello.f90 > print *,"Hello, world!" > end > $ 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 :-( > > Is there a way to configure the build so that the old debug > format is used for the libraries? > > Best regards > > Thomas ----------------- Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München / Germany Registergericht München HRB 106955, Geschäftsführer: Thomas Heurung, Alexander Walter ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Non-dwarf blocks detected by valgrind 2021-01-25 14:40 ` Tobias Burnus @ 2021-01-25 14:55 ` Thomas Koenig 0 siblings, 0 replies; 5+ messages in thread From: Thomas Koenig @ 2021-01-25 14:55 UTC (permalink / raw) To: Tobias Burnus, Paul Richard Thomas; +Cc: gcc mailing list, fortran Hi Tobias, > which binutil version do you have? $ as -v GNU assembler version 2.35.1 (x86_64-suse-linux) using BFD version (GNU Binutils; openSUSE Leap 15.1) 2.35.1.20201123-lp151.3.12 > I am asking because Jakub just > submitted: > https://gcc.gnu.org/pipermail/gcc-patches/2021-January/564206.html Looks like this could be the issue. I'll re-check once that patch has hit the trunk. Best regards Thomas ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-01-25 17:09 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAGkQGiLV78AKY=GtoVq+0rbuUQWLFu5maEQ7bMa4tHbLMXfmjA@mail.gmail.com>
[not found] ` <f5a2e723-4998-4459-c0d1-0de721cdefa6@net-b.de>
[not found] ` <CAGkQGiJV9m8atjc_8tcqq1Z3tBk33WXp3e-mk2moP72yXx5-tw@mail.gmail.com>
[not found] ` <362769a6-4184-e59b-ded1-7cbe972c84ba@codesourcery.com>
2021-01-25 14:05 ` Non-dwarf blocks detected by valgrind Thomas Koenig
2021-01-25 14:38 ` Mark Wielaard
2021-01-25 17:08 ` Mark Wielaard
2021-01-25 14:40 ` Tobias Burnus
2021-01-25 14:55 ` Thomas Koenig
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).