Package: gdb Version: 7.12-4 Severity: normal When I've upgraded a library or a binary and then subsequently try to create a backtrace from a core file created before the upgrade, I get a warning about a mismatch between the core file and the executable but the warning is completely annoyingly non-actionable because it doesn't include any information about build-ids so I can't lookup the old ones on build-id.debian.net and download the binary packages from the snapshot.debian.org service. The warnings about libraries should also be printing out mismatched build-ids.
warning: core file may not match specified executable file. -- System Information: Debian Release: stretch/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gdb depends on: ii libbabeltrace-ctf1 1.5.0-1 ii libbabeltrace1 1.5.0-1 ii libc6 2.24-8 ii libexpat1 2.2.0-2 ii liblzma5 5.2.2-1.2 ii libncurses5 6.0+20161126-1 ii libpython3.5 3.5.2-9 ii libreadline7 7.0-1 ii libtinfo5 6.0+20161126-1 ii zlib1g 1:1.2.8.dfsg-4 Versions of packages gdb recommends: ii libc6-dbg [libc-dbg] 2.24-8 Versions of packages gdb suggests: ii gdb-doc 7.12-2 ii gdbserver 7.12-4 -- debconf-show failed -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
