Hi, On 2023-12-11 23:05, Felix Geyer wrote: > On Fri, 8 Dec 2023 15:48:27 +0100 Emanuele Rocca <e...@debian.org> wrote: > > Hi Simon, > > > > On 2023-12-07 08:39, Simon Josefsson wrote: > > > During debci autopkgtest of a new version of libgssglue on i386 I got > > > a failure like this, which is fatal and execution halts. > > > > > > 117s vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26 > > > > The problem can be reproduced with valgrind 3.19 as well: > > > > $ autopkgtest --shell-fail libgssglue_0.8-1.dsc > ~/Downloads/valgrind_3.19.0-1_i386.deb -- schroot sid-i386-sbuild > > > > [...] > > > > (sid-i386-sbuild)root@ariel:/tmp/autopkgtest.lmoplT/build.hLF/src# > valgrind /usr/bin/gsasl 2>&1 | grep ^vex > > vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26 > > (sid-i386-sbuild)root@ariel:/tmp/autopkgtest.lmoplT/build.hLF/src# valgrind > > --version > > valgrind-3.19.0
Starting with binutils 2.41.50.20231125-1, and more precisely starting with the following upstream commit, 2e 8d b4 26 00 00 00 is now generated as a one of the NOP patterns: https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=ad9f3230565ca40bfa1d9a3106aaaa272cb125f2 > I'm pretty sure this is caused by glibc 2.37-13 glibc 2.37-13 is just one of the numerous packages that have been rebuilt with binutils 2.41.50.20231125-1 or later. For instance I have also spotted gcc 13.2.0-8 on debci. The real issue is in valgrind, which has to be fixed to support this NOP pattern. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
