Package: valgrind
Version: 1:3.9.0-1
Severity: wishlist
It would be great if valgrind could ship memcheck.h and friends, and
valgrind.pc, in a new valgrind-dev or valgrind-headers or something on all
architectures; then packages that consume them, like dbus, wouldn't have
to stay in sync with valgrind's architecture list (leading to RC bugs
like #729136 when valgrind drops an architecture).
Looking at those headers, the declarations already seem to expand to
nothing on platforms not supported by valgrind?
Thanks,
S
-- System Information:
Debian Release: jessie/sid
APT prefers proposed-updates
APT policy: (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages valgrind depends on:
ii libc6 2.17-97
ii libc6-dbg 2.17-97
Versions of packages valgrind recommends:
ii gdb 7.6.1-1
ii valgrind-dbg 1:3.9.0-1
Versions of packages valgrind suggests:
pn alleyoop <none>
ii kcachegrind 4:4.11.3-1
pn valgrind-mpi <none>
pn valkyrie <none>
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
