* Non-dwarf blocks detected by valgrind
@ 2021-01-23 8:52 Paul Richard Thomas
2021-01-23 10:51 ` Tobias Burnus
0 siblings, 1 reply; 11+ messages in thread
From: Paul Richard Thomas @ 2021-01-23 8:52 UTC (permalink / raw)
To: fortran
Hi All,
Has anybody else seen this popping up in executables produced from master?
[pault@pc30 pr64290]$ valgrind ./a.out -s
==1627334== Memcheck, a memory error detector
==1627334== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1627334== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright
info
==1627334== Command: ./a.out -s
==1627334==
--1627334-- WARNING: Serious error when reading debug info
--1627334-- When reading debug info from /home/pault/prs/pr64290/a.out:
--1627334-- Ignoring non-Dwarf2/3/4 block in .debug_info
,,,,,repeats many times
--1627334-- WARNING: Serious error when reading debug info
--1627334-- When reading debug info from /home/pault/prs/pr64290/a.out:
--1627334-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
==1627334==
==1627334== HEAP SUMMARY:
==1627334== in use at exit: 0 bytes in 0 blocks
==1627334== total heap usage: 42 allocs, 42 frees, 13,691 bytes allocated
==1627334==
==1627334== All heap blocks were freed -- no leaks are possible
==1627334==
==1627334== For lists of detected and suppressed errors, rerun with: -s
==1627334== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Paul
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Non-dwarf blocks detected by valgrind
2021-01-23 8:52 Non-dwarf blocks detected by valgrind Paul Richard Thomas
@ 2021-01-23 10:51 ` Tobias Burnus
2021-01-23 13:32 ` Paul Richard Thomas
0 siblings, 1 reply; 11+ messages in thread
From: Tobias Burnus @ 2021-01-23 10:51 UTC (permalink / raw)
To: Paul Richard Thomas; +Cc: fortran
Hi Paul,
On 23.01.21 09:52, Paul Richard Thomas via Fortran wrote:
> Has anybody else seen this popping up in executables produced from master?
>
> --1627334-- Ignoring non-Dwarf2/3/4 block in .debug_info
This error looks as if Valgrind does not support DWARF5. Try to compile
with -gdwarf-4.
GCC switched to defaulting to DWARF 5 in GCC 11, cf.
https://gcc.gnu.org/g:3804e937b0e252a7e42632fe6d9f898f1851a49c (Mark
Wielaard; committed 17 Jan 2021).
(Not yet documented in the release notes.)
Cheers,
Tobias
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Non-dwarf blocks detected by valgrind
2021-01-23 10:51 ` Tobias Burnus
@ 2021-01-23 13:32 ` Paul Richard Thomas
2021-01-24 20:37 ` Thomas Koenig
2021-01-25 7:33 ` Tobias Burnus
0 siblings, 2 replies; 11+ messages in thread
From: Paul Richard Thomas @ 2021-01-23 13:32 UTC (permalink / raw)
To: Tobias Burnus; +Cc: fortran
Hi Tobias,
Thanks for the quick reply. However, -gdwarf-4 does not quieten valgrind
down.
Does this constitute a regression?
Cheers
Paul
On Sat, 23 Jan 2021 at 10:51, Tobias Burnus <burnus@net-b.de> wrote:
> Hi Paul,
>
> On 23.01.21 09:52, Paul Richard Thomas via Fortran wrote:
> > Has anybody else seen this popping up in executables produced from
> master?
> >
> > --1627334-- Ignoring non-Dwarf2/3/4 block in .debug_info
>
> This error looks as if Valgrind does not support DWARF5. Try to compile
> with -gdwarf-4.
>
> GCC switched to defaulting to DWARF 5 in GCC 11, cf.
> https://gcc.gnu.org/g:3804e937b0e252a7e42632fe6d9f898f1851a49c (Mark
> Wielaard; committed 17 Jan 2021).
>
> (Not yet documented in the release notes.)
>
> Cheers,
>
> Tobias
>
>
--
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Non-dwarf blocks detected by valgrind
2021-01-23 13:32 ` Paul Richard Thomas
@ 2021-01-24 20:37 ` Thomas Koenig
2021-01-24 21:47 ` Paul Richard Thomas
2021-01-25 7:33 ` Tobias Burnus
1 sibling, 1 reply; 11+ messages in thread
From: Thomas Koenig @ 2021-01-24 20:37 UTC (permalink / raw)
To: Paul Richard Thomas, Tobias Burnus; +Cc: fortran
Hi Paul,
> Thanks for the quick reply. However, -gdwarf-4 does not quieten valgrind
> down.
>
> Does this constitute a regression?
Very much so, IMHO.
Do you want to submit the bug report?
Best regards
Thomas
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Non-dwarf blocks detected by valgrind
2021-01-24 20:37 ` Thomas Koenig
@ 2021-01-24 21:47 ` Paul Richard Thomas
0 siblings, 0 replies; 11+ messages in thread
From: Paul Richard Thomas @ 2021-01-24 21:47 UTC (permalink / raw)
To: Thomas Koenig; +Cc: Tobias Burnus, fortran
OK - I'll get on to it tomorrow.
Thanks
Paul
On Sun, 24 Jan 2021 at 20:37, Thomas Koenig <tkoenig@netcologne.de> wrote:
> Hi Paul,
>
> > Thanks for the quick reply. However, -gdwarf-4 does not quieten valgrind
> > down.
> >
> > Does this constitute a regression?
>
> Very much so, IMHO.
>
> Do you want to submit the bug report?
>
> Best regards
>
> Thomas
>
--
"If you can't explain it simply, you don't understand it well enough" -
Albert Einstein
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Non-dwarf blocks detected by valgrind
2021-01-23 13:32 ` Paul Richard Thomas
2021-01-24 20:37 ` Thomas Koenig
@ 2021-01-25 7:33 ` Tobias Burnus
2021-01-25 14:05 ` Thomas Koenig
1 sibling, 1 reply; 11+ messages in thread
From: Tobias Burnus @ 2021-01-25 7:33 UTC (permalink / raw)
To: Paul Richard Thomas; +Cc: fortran
Hi Paul,
On 23.01.21 14:32, Paul Richard Thomas wrote:
> Thanks for the quick reply. However, -gdwarf-4 does not quieten valgrind down.
Works here, trying with the third attachment to PR64290,
current GCC on x86_64-gnu-linux, and Valgrind-3.15.0 of
Ubuntu focal (20.04.1 LTS).
With "gfortran -g" (or "gfortran -gdwarf-5), I get:
--721834-- WARNING: Serious error when reading debug info
--721834-- When reading debug info from /dev/shm/a.out:
--721834-- Ignoring non-Dwarf2/3/4 block in .debug_info
But when I use "gfortran -gdwarf-4" (or "gfortran -g -gdwarf-4"), no error is shown.
> Does this constitute a regression?
From your description, yes. Can you give more details how to reproduce it?
Tobias
-----------------
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] 11+ messages in thread
* Re: Non-dwarf blocks detected by valgrind
2021-01-25 7:33 ` Tobias Burnus
@ 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; 11+ 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] 11+ messages in thread
* Re: Non-dwarf blocks detected by valgrind
2021-01-25 14:05 ` 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; 11+ 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] 11+ 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; 11+ 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] 11+ messages in thread
* Re: Non-dwarf blocks detected by valgrind
2021-01-25 14:05 ` 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; 11+ 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] 11+ messages in thread
end of thread, other threads:[~2021-01-25 17:09 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-23 8:52 Non-dwarf blocks detected by valgrind Paul Richard Thomas
2021-01-23 10:51 ` Tobias Burnus
2021-01-23 13:32 ` Paul Richard Thomas
2021-01-24 20:37 ` Thomas Koenig
2021-01-24 21:47 ` Paul Richard Thomas
2021-01-25 7:33 ` Tobias Burnus
2021-01-25 14:05 ` 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).