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
Hi Tobias,
which binutil version do you have?
$ as -v
GNU assembler version 2.35.1 (x86_64-suse-linux) using BFD version (GNU
Binutils; openSUSE Leap 15.1) 2.35.1.20201123-lp151.3.12
I am asking because Jakub just
submitted:
https://gcc.gnu.org/pipermail/gcc-patches/2021-January/564206.
Hi Thomas,
which binutil version do you have? I am asking because Jakub just
submitted:
https://gcc.gnu.org/pipermail/gcc-patches/2021-January/564206.html
If that does not help, it might be that valgrind simply does not like
the DWARF which GCC now produces by default.
Defaulting to 4: Well, on
Hi,
On Mon, 2021-01-25 at 15:05 +0100, Thomas Koenig via Gcc wrote:
> $ valgrind --version
> valgrind-3.15.0
> $ gfortran -g hello.f90
> $ valgrind ./a.out
> [...]
> --4184-- WARNING: Serious error when reading debug info
> --4184-- When reading debug info from
> /home/ig25/lib64/libgfortran.so.5.
Hi Tobias,
Does this constitute a regression?
From your description, yes. Can you give more details how to reproduce it?
$ cat hello.f90
print *,"Hello, world!"
end
$ valgrind --version
valgrind-3.15.0
$ gfortran -g hello.f90
$ valgrind ./a.out
[...]
--4184-- WARNING: Serious error when
