Package: valgrind
Version: 1:3.13.0-2+b1
Followup-For: Bug #701480

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


This has gotten worse with current binutils, now valgrind seems unable to make 
use of even uncompressed debugging symbols.

Is there a solution in sight?


- -- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), 
(102, 'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.5+ (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages valgrind depends on:
ii  libc6      2.27-4
ii  libc6-dbg  2.27-4

Versions of packages valgrind recommends:
ii  gdb           7.12-6+b2
ii  valgrind-dbg  1:3.13.0-2+b1

Versions of packages valgrind suggests:
pn  alleyoop      <none>
ii  kcachegrind   4:17.08.3-2
pn  valgrind-mpi  <none>
pn  valkyrie      <none>

- -- no debconf information

-----BEGIN PGP SIGNATURE-----

iHEEARECADEWIQSwn681vpFFIZgJURRaga+OatuyAAUCW0SLaBMcbWljaGVsQGRh
ZW56ZXIubmV0AAoJEFqBr45q27IAGBQAnjyZEEjrGsdhHoWGwVWDbPxmSmAuAJ4q
7wpHBPR/dOKJ8oGhURidaND3ng==
=jOhS
-----END PGP SIGNATURE-----

Reply via email to