Package: valgrind
Version: 1:3.12.0~svn20160714-1+b1
Severity: serious
Tags: upstream
Justification: 4
Dear Maintainer,
* What led up to the situation?
valgrind ./myprog
* What exactly did you do (or not do) that was effective (or
ineffective)?
Looks like an upstream bug that was fixed:
https://bugs.kde.org/show_bug.cgi?id=362935
-- System Information:
Debian Release: 9.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 4.4.132+ (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages valgrind depends on:
ii libc6 2.24-11+deb9u4
ii libc6-dbg 2.24-11+deb9u4
Versions of packages valgrind recommends:
ii gdb 7.12-6
pn valgrind-dbg <none>
Versions of packages valgrind suggests:
pn alleyoop <none>
pn kcachegrind <none>
pn valgrind-mpi <none>
pn valkyrie <none>
-- no debconf information
