Your message dated Wed, 18 Jul 2018 22:06:41 +0000 with message-id <[email protected]> and subject line Bug#903389: fixed in valgrind 1:3.13.0-2.1 has caused the Debian Bug report #903389, regarding binutils: new binutils version breaks valgrind, can't determine stacktraces to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 903389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903389 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: binutils Version: 2.30.90.20180705-1 Severity: normal Hi, after upgrading binutils (from 2.30-22 to 2.30.90.20180705-1) *newly* built binaries don't work well with valgrind anymore. Binaries built with an older version of binutils, verified by downgrading, continue to work well with valgrind. The stack traces after the upgrade are useless. This both makes using valgrind nearly pointless, as well as breaking valgrind suppression files (which rely on useful backtraces). A trivial example is the following: $ dpkg-query --showformat='${Version}' --show binutils 2.30-22 $ cat ~/tmp/uninitialized.c int main(int argc, char **argv) { int foo; if (foo == 3) return 0; else return 1; } $ gcc ~/tmp/uninitialized.c -o uninitialized $ valgrind ./uninitialized ... ==16745== Conditional jump or move depends on uninitialised value(s) ==16745== at 0x108609: main (in /home/andres/tmp/uninitialized) .. # dpkg -i *binutils*2.30.90* $ dpkg-query --showformat='${Version}\n' --show binutils 2.30.90.20180627-1 $ gcc ~/tmp/uninitialized.c -o uninitialized ... ==18603== Conditional jump or move depends on uninitialised value(s) ==18603== at 0x109159: ??? (in /home/andres/tmp/uninitialized) ==18603== by 0x4CADB16: ??? (in /lib/x86_64-linux-gnu/libc-2.27.so) ... but if I force gold to be used: $ gcc -fuse-ld=gold ~/tmp/uninitialized.c -o uninitialized $ valgrind ./uninitialized .... ==18665== Conditional jump or move depends on uninitialised value(s) ==18665== at 0x108619: main (in /home/andres/tmp/uninitialized) so this seems somewhat likely to be related to GNU ld changes, rather than a valgrind issue. I haven't yet figured out which of the changes between the two versions is to blame - Andres
--- End Message ---
--- Begin Message ---Source: valgrind Source-Version: 1:3.13.0-2.1 We believe that the bug you reported is fixed in the latest version of valgrind, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ansgar Burchardt <[email protected]> (supplier of updated valgrind package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 18 Jul 2018 23:21:57 +0200 Source: valgrind Binary: valgrind valgrind-dbg valgrind-mpi Architecture: source Version: 1:3.13.0-2.1 Distribution: unstable Urgency: high Maintainer: Alessandro Ghedini <[email protected]> Changed-By: Ansgar Burchardt <[email protected]> Description: valgrind - instrumentation framework for building dynamic analysis tools valgrind-dbg - instrumentation framework for building dynamic analysis tools (de valgrind-mpi - instrumentation framework for building dynamic analysis tools (MP Closes: 903389 Changes: valgrind (1:3.13.0-2.1) unstable; urgency=high . * Non-maintainer upload. * backport: Accept read-only PT_LOAD segments and .rodata (Closes: #903389) + new patch: 12_Accept-read-only-PT_LOAD-segments-and-.rodata.patch Checksums-Sha1: e874c9d07204ddbcc4390e1511bece09400bf4e0 2448 valgrind_3.13.0-2.1.dsc d66a839b9ec5432e20fe9b7647f252a5916cf802 28300 valgrind_3.13.0-2.1.debian.tar.xz Checksums-Sha256: ce9f54d5d12b377c1a8554369c4366a94bc2a9a819ac2283d02f035a47c3ad45 2448 valgrind_3.13.0-2.1.dsc d353075b6faa7054451f21c294da1c156defff8137a14d27e0b8e7aaf5169f7c 28300 valgrind_3.13.0-2.1.debian.tar.xz Files: f7dd84aa5a73039f7cac4c8d4eb1b7f1 2448 devel optional valgrind_3.13.0-2.1.dsc 6e8b66ce0e7298f0579a840cc24f4ad3 28300 devel optional valgrind_3.13.0-2.1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAltPuFESHGFuc2dhckBk ZWJpYW4ub3JnAAoJEGpjAo9adOiTAuEP/j211d17lbrbg+98dEsec1ruuWc8++Wv 1HxOwwLBGFySrdb5QZe1GTQqO+deFiQ72d1lt+VygUpetka8kX8OTCzIqknQjRbu VinRah2J/edrwT/mLSzyoQpxa3NbKUNtkZQ9POIlJf53lqYvKQYWNGCg2X6lHQX/ 7KaUZV4EEOXbk8aJnImwad4Zi5Fzra5c4ZuXTGk4GAXjKs1zF/SXWbR2Ce8xZkUQ EF+3Cyaskr4GM0CURp9qCOQL4R7C9chrU1AyaXZm02Ttf3B8hLSh++4j9EztmCPr QASTWvLXWGwBx9ML/1q1zk4Z8gyA/6ei6gCgoDKPZ/w/ZuzVVIvcKg2uWMi0PfLj Xn3qdcOUsVW5u74RotcU+pPSGDbJ5l6NUkQgi8IGadBCzC/AwOrtgeU55R8Q/YPX TDBMDAAkgaEE817yE7er8Poi/Ryj26HkLv1X69u0861cfoHRb581liMVJ1DyywHw WdQ3fi90HUzUb6deoUXn/1Kc3rWJJrhA5J+eax0wUZS1YNKFiJX0RkSuKo3xgfOj xG/wA/7EWp7FWtdAMy6TWH5eMYACLZ7wnD11DocBb+hLxvTvz8cMOFKSQJQi0/o3 /91bGGwExt5YCyoJwNAVloTAaGHmcnuNRGGuXH5c7h5Qp0+gwKnU3+2PTZHVP/jg jxCFYOSs6gYa =nrQt -----END PGP SIGNATURE-----
--- End Message ---
