FS#56294 - [gcc-libs][valgrind] Valgrind reports serious error when reading debug info from libgfortran.so

Attached to Project: Arch Linux
Opened by Andrew A (andrew-wja) - Friday, 10 November 2017, 14:33 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Friday, 05 January 2018, 08:29 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Bartłomiej Piotrowski (Barthalion)
Levente Polyak (anthraxx)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

[andrew@desktop build]$ valgrind --tool=exp-sgcheck ./debug-scenario-0
==6432== exp-sgcheck, a stack and global array overrun detector
==6432== NOTE: This is an Experimental-Class Valgrind Tool
==6432== Copyright (C) 2003-2017, and GNU GPL'd, by OpenWorks Ltd et al.
==6432== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==6432== Command: ./debug-scenario-0
==6432==

parse DIE(readdwarf3.c:3619): confused by:
<2><17a0cc>: Abbrev Number: 10 (DW_TAG_subrange_type)
DW_AT_type : <17a0ea>
DW_AT_upper_bound : <17a068>
parse_type_DIE:
--6432-- WARNING: Serious error when reading debug info
--6432-- When reading debug info from /usr/lib/libgfortran.so.4.0.0:
--6432-- confused by the above DIE


Additional info:
* package version(s)
- gcc-libs-7.2.0-3
- valgrind-3.13.0-3

Steps to reproduce:

Compile any program with -g and link with -lgfortran. Run valgrind on the resulting executable.
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Friday, 05 January 2018, 08:29 GMT
Reason for closing:  Upstream
Additional comments about closing:  Not a packaging issue.
Comment by Bartłomiej Piotrowski (Barthalion) - Wednesday, 03 January 2018, 13:01 GMT
Looks like it happens only if libgfortran isn't stripped from debug symbols, and doesn't cause valgrind to exit. Investigating where the actual bug is.
Comment by Bartłomiej Piotrowski (Barthalion) - Wednesday, 03 January 2018, 13:44 GMT
Reported upstream as I fail to see anything relevant: https://bugs.kde.org/show_bug.cgi?id=388493

Loading...