public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: Tobias Burnus <burnus@net-b.de>
Cc: fortran <fortran@gcc.gnu.org>
Subject: Re: Non-dwarf blocks detected by valgrind
Date: Sat, 23 Jan 2021 13:32:06 +0000	[thread overview]
Message-ID: <CAGkQGiJV9m8atjc_8tcqq1Z3tBk33WXp3e-mk2moP72yXx5-tw@mail.gmail.com> (raw)
In-Reply-To: <f5a2e723-4998-4459-c0d1-0de721cdefa6@net-b.de>

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

  reply	other threads:[~2021-01-23 13:32 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 [this message]
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

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=CAGkQGiJV9m8atjc_8tcqq1Z3tBk33WXp3e-mk2moP72yXx5-tw@mail.gmail.com \
    --to=paul.richard.thomas@gmail.com \
    --cc=burnus@net-b.de \
    --cc=fortran@gcc.gnu.org \
    /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).