From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mark@klomp.org>
Received: from gnu.wildebeest.org (wildebeest.demon.nl [212.238.236.112])
 by sourceware.org (Postfix) with ESMTPS id B9ED8385781A;
 Mon, 25 Jan 2021 17:09:01 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B9ED8385781A
Authentication-Results: sourceware.org;
 dmarc=none (p=none dis=none) header.from=klomp.org
Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=mark@klomp.org
Received: from tarox.wildebeest.org (tarox.wildebeest.org [172.31.17.39])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by gnu.wildebeest.org (Postfix) with ESMTPSA id 3C7923000850;
 Mon, 25 Jan 2021 18:08:59 +0100 (CET)
Received: by tarox.wildebeest.org (Postfix, from userid 1000)
 id D26A24000BC8; Mon, 25 Jan 2021 18:08:59 +0100 (CET)
Message-ID: <6bdf08d6bfd5bf7e9fabc2839f2133d7268f9835.camel@klomp.org>
Subject: Re: Non-dwarf blocks detected by valgrind
From: Mark Wielaard <mark@klomp.org>
To: Thomas Koenig <tkoenig@netcologne.de>, Tobias Burnus
 <tobias@codesourcery.com>, Paul Richard Thomas
 <paul.richard.thomas@gmail.com>
Cc: gcc mailing list <gcc@gcc.gnu.org>, fortran <fortran@gcc.gnu.org>
Date: Mon, 25 Jan 2021 18:08:59 +0100
In-Reply-To: <3052033658e9bd93ece536193efe6fa8276837b7.camel@klomp.org>
References: <CAGkQGiLV78AKY=GtoVq+0rbuUQWLFu5maEQ7bMa4tHbLMXfmjA@mail.gmail.com>
 <f5a2e723-4998-4459-c0d1-0de721cdefa6@net-b.de>
 <CAGkQGiJV9m8atjc_8tcqq1Z3tBk33WXp3e-mk2moP72yXx5-tw@mail.gmail.com>
 <362769a6-4184-e59b-ded1-7cbe972c84ba@codesourcery.com>
 <c5627671-2fce-1304-f451-6d8cc08f0c3f@netcologne.de>
 <3052033658e9bd93ece536193efe6fa8276837b7.camel@klomp.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Evolution 3.28.5 (3.28.5-10.el7) 
Mime-Version: 1.0
X-Spam-Status: No, score=-5.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KAM_SHORT, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: fortran@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Fortran mailing list <fortran.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/fortran>,
 <mailto:fortran-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/fortran/>
List-Help: <mailto:fortran-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/fortran>,
 <mailto:fortran-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jan 2021 17:09:03 -0000

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
> >=20
> > 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 :-(
>=20
> I have a patch for that:
> https://code.wildebeest.org/git/user/mjw/valgrind/commit/?h=3Ddwarf5
>=20
> 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=3D432102
Also backported to Fedora 34 valgrind package:
https://bodhi.fedoraproject.org/updates/FEDORA-2021-6335fad95d

Cheers,

Mark