From: Paul Richard Thomas <paul.richard.thomas@gmail.com>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Non-dwarf blocks detected by valgrind
Date: Sat, 23 Jan 2021 08:52:11 +0000 [thread overview]
Message-ID: <CAGkQGiLV78AKY=GtoVq+0rbuUQWLFu5maEQ7bMa4tHbLMXfmjA@mail.gmail.com> (raw)
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
next reply other threads:[~2021-01-23 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 8:52 Paul Richard Thomas [this message]
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
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='CAGkQGiLV78AKY=GtoVq+0rbuUQWLFu5maEQ7bMa4tHbLMXfmjA@mail.gmail.com' \
--to=paul.richard.thomas@gmail.com \
--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).