From: Tobias Burnus <tobias@codesourcery.com>
To: Paul Richard Thomas <paul.richard.thomas@gmail.com>
Cc: fortran <fortran@gcc.gnu.org>
Subject: Re: Non-dwarf blocks detected by valgrind
Date: Mon, 25 Jan 2021 08:33:34 +0100 [thread overview]
Message-ID: <362769a6-4184-e59b-ded1-7cbe972c84ba@codesourcery.com> (raw)
In-Reply-To: <CAGkQGiJV9m8atjc_8tcqq1Z3tBk33WXp3e-mk2moP72yXx5-tw@mail.gmail.com>
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
next prev parent reply other threads:[~2021-01-25 7:33 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 [this message]
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
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=362769a6-4184-e59b-ded1-7cbe972c84ba@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=fortran@gcc.gnu.org \
--cc=paul.richard.thomas@gmail.com \
/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).