Package: valgrind
Version: 1:3.15.0-1
Severity: normal

Dear Maintainer,

I wish for  valgrind:i386 and valgrind:amd64 to be installable at the same
time, for cross-architecture debugging.

The binary tools, could have prefixes, and the legacy symlinks using alternative
mechanisms.

Headers and documentation should go into arch independent libvalgrind-dev and
libvalgrind/valgrind-doc packages, and manpages should go into corresponding
valgrind:arch package, and by the same on both architectures.

I think header files and the valgrind library should go into a separate package
anyway, becasue it is possible, and common to use valgrind binary without them,
i.e. to debug non-valgrind instrumented binaries, so it doesn't make that much
sense to bundled them into valgrind:arch package.

Thank you.

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages valgrind depends on:
ii  libc6      2.29-2
ii  libc6-dbg  2.29-2

Versions of packages valgrind recommends:
ii  gdb           8.3-1
ii  valgrind-dbg  1:3.15.0-1

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

Reply via email to