From: Tobias Burnus <tobias@codesourcery.com>
To: Thomas Koenig <tkoenig@netcologne.de>,
Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Subject: Re: Non-dwarf blocks detected by valgrind
Date: Mon, 25 Jan 2021 15:40:47 +0100 [thread overview]
Message-ID: <6231d760-3cec-14a8-4e78-82bae4fe26ed@codesourcery.com> (raw)
In-Reply-To: <c5627671-2fce-1304-f451-6d8cc08f0c3f@netcologne.de>
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
next prev parent reply other threads:[~2021-01-25 14:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 8:52 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 [this message]
2021-01-25 14:55 ` Thomas Koenig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6231d760-3cec-14a8-4e78-82bae4fe26ed@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
--cc=tkoenig@netcologne.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).