Your message dated Tue, 2 Jan 2024 13:53:31 +0100 with message-id <zzqhs05_zbbrq...@aurel32.net> and subject line Re: valgrind: i386 vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26 has caused the Debian Bug report #1057693, regarding valgrind: i386 vex x86->IR: unhandled instruction bytes: 0x2E 0x8D 0xB4 0x26 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 ow...@bugs.debian.org immediately.) -- 1057693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: valgrind Version: 1:3.20.0-2 Hi. 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 117s ==5711== valgrind: Unrecognised instruction at address 0x4d285c8. 117s ==5711== at 0x4D285C8: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711== by 0x4D27893: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711== by 0x4D27B0E: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711== by 0x4D27069: gss_import_name (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711== by 0x486BA0F: ??? (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711== by 0x485757C: gsasl_step (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711== by 0x4857623: gsasl_step64 (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711== by 0x10B387: ??? (in /usr/bin/gsasl) 117s ==5711== by 0x4ADE7C4: (below main) (libc_start_call_main.h:58) 117s ==5711== Your program just tried to execute an instruction that Valgrind 117s ==5711== did not recognise. There are two possible reasons for this. 117s ==5711== 1. Your program has a bug and erroneously jumped to a non-code 117s ==5711== location. If you are running Memcheck and you just saw a 117s ==5711== warning about a bad jump, it's probably your program's fault. 117s ==5711== 2. The instruction is legitimate but Valgrind doesn't handle it, 117s ==5711== i.e. it's Valgrind's fault. If you think this is the case or 117s ==5711== you are not sure, please let us know and we'll try to fix it. 117s ==5711== Either way, Valgrind will now raise a SIGILL signal which will 117s ==5711== probably kill your program. 117s ==5711== 117s ==5711== Process terminating with default action of signal 4 (SIGILL) 117s ==5711== Illegal opcode at address 0x4D285C8 117s ==5711== at 0x4D285C8: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711== by 0x4D27893: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711== by 0x4D27B0E: ??? (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711== by 0x4D27069: gss_import_name (in /usr/lib/i386-linux-gnu/libgssglue.so.1.0.0) 117s ==5711== by 0x486BA0F: ??? (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711== by 0x485757C: gsasl_step (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711== by 0x4857623: gsasl_step64 (in /usr/lib/i386-linux-gnu/libgsasl.so.18.0.0) 117s ==5711== by 0x10B387: ??? (in /usr/bin/gsasl) 117s ==5711== by 0x4ADE7C4: (below main) (libc_start_call_main.h:58) I can reproduce this in debian sid like this, on my amd64 laptop: podman run --arch 386 -it --rm debian:unstable-slim apt update apt install valgrind gsasl apt dist-upgrade valgrind --error-exitcode=1 /usr/bin/gsasl -m GSSAPI -d --no-starttls --imap no-such-domain.example 143 Running it without valgrind works: /usr/bin/gsasl -m GSSAPI -d --no-starttls --imap no-such-domain.example 143 /usr/bin/gsasl: no-such-domain.example: Name or service not known However running it under gdb doesn't seem to work either: root@65b9c363c623:/# gdb --silent /usr/bin/gsasl Reading symbols from /usr/bin/gsasl... (No debugging symbols found in /usr/bin/gsasl) (gdb) r -m GSSAPI -d --no-starttls --imap no-such-domain.example 143 Starting program: /usr/bin/gsasl -m GSSAPI -d --no-starttls --imap no-such-domain.example 143 warning: Error disabling address space randomization: Success warning: Could not trace the inferior process. warning: ptrace: Operation not permitted During startup program exited with code 127. The build log for this libgssglue on i386 (built just a day ago in debian sid) is here: https://buildd.debian.org/status/fetch.php?pkg=libgssglue&arch=i386&ver=0.8-1&stamp=1701797253&raw=0 Libgssglue is a simple C library with no dependencies, and no complexity in the build system, but do you notice anything odd with the compiler settings here that could cause it to generate unwanted instructions? If the libgssglue library doesn't contain unwanted instructions, isn't this a valgrind bug? If relevant, the build log for gsasl is here: https://buildd.debian.org/status/fetch.php?pkg=gsasl&arch=i386&ver=2.2.0-2&stamp=1689109164&raw=0 Do you spot anything odd in that? This build was long ago, on a much older sid so maybe something changed meanwhile. I look at the debci output on i386 for libgssglue 0.7-2 which passed, and it looks like this: https://ci.debian.net/packages/libg/libgssglue/testing/i386/40704726/ Notice the 'Illegal instruction' outputs directly when starting 'gsasl', which causes the self-test to not use valgrind at all. In the new 0.8 debci output, you can see that several self-tests for 'gsasl' works under valgrind, it is just when it comes to libgssglue code that it triggers the 'Illegal instruction'. I will disable use of valgrind on i386 during debci/autopkgtest until I can figure out how to fix this problem. Currently libgssglue's autopkgtest depends on 'valgrind-if-available' which results in use of valgrind on all platforms where Debian provides it. /Simon
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Version: 1:3.20.0-2.1 On 2024-01-02 13:17, Aurelien Jarno wrote: > Hi, > > I have done a NMU to fix this issue blocking the migration of many > packages to testing. Please find the debdiff attached. It seems I made a typo in the changelog, so the bug hasn't been closed automatically with the upload. Fixing that with that mail: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 02 Jan 2024 12:09:38 +0000 Source: valgrind Architecture: source Version: 1:3.20.0-2.1 Distribution: unstable Urgency: medium Maintainer: Alessandro Ghedini <gh...@debian.org> Changed-By: Aurelien Jarno <aure...@debian.org> Changes: valgrind (1:3.20.0-2.1) unstable; urgency=medium . * Non-maintainer upload. * Apply fix from upstream to add support for new x86 nops patterns. Closes #1057693. Checksums-Sha1: f2d88b71b07dff44367f7e188edfc777b038a0ed 2355 valgrind_3.20.0-2.1.dsc 403be52ab09c63f45714a7ffa9a85df37293e599 29068 valgrind_3.20.0-2.1.debian.tar.xz 176579872396e4983c4b07ca4a27e8313e924fc1 8890 valgrind_3.20.0-2.1_source.buildinfo Checksums-Sha256: 53d687a10161f504231fefea0ec61ef3adcdba4ed237cf79e7da18b5c2a3b26a 2355 valgrind_3.20.0-2.1.dsc 321d4aa02f4f142b95e58454e950823f341c74e1ea6fa3072a6d76b2cef27adf 29068 valgrind_3.20.0-2.1.debian.tar.xz cbac9f6a337db40362b8cbc924d816be7d2fc1822cba9e07e11d73e47e886ef9 8890 valgrind_3.20.0-2.1_source.buildinfo Files: c0cbb338d1396cba78beffab70c6bbde 2355 devel optional valgrind_3.20.0-2.1.dsc 4b2d7cf01143ebf124d76fb539527124 29068 devel optional valgrind_3.20.0-2.1.debian.tar.xz 6be7156c863a9283b84d4fd9ae5b30fe 8890 devel optional valgrind_3.20.0-2.1_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAmWT/lkACgkQE4jA+Jno M2sZNQ/+LB5XcQctcVkyw/K117ig0x9S7vkz45aZF+VljVkhVpAxaNbElcS/CvpR Ej0hraQbVzsxFWiGlnPh4EQaVmED5Z99oLPX8tIa78xBmRWXycsEJi0bwyWMaEcw up3ypGJtyazW0YepnMRCiRhVLORqoKfQQ0lBG2DePDr5KShYaPAJsC2NCJJzQGbY jm2ljosz/Xa6hEQjUo6bp9PA5yP2mDhNTAiNWpMB1sQD2KzK6WG16AdwP4eCY/TA ZnjzRfafE7SmeYc720QSBihqZQK+13BDUSKtG0FEMNCk7XPxnhkUcoH0UPVmkORE J+adK0MkEYeYywHUzrlKBW2aAsxUPOdR8MCPpk2uU8PZu70z6EgUb8SKOEgAaKm3 LRkJaiCQxTqmcQj+v5INlK+tc/FTjZDSiwZbqyveEs/fyqOmI3Zu/1qeBhiycfmU ScwlMwpa2pdqQYh6ZHvX7yDmsRXTZD1BMARWMB0F95rhJY5p4wXs6n493Vuhk1VH yV8zmk/RADI43XTzqm38E4Xo+6EYdUgzDLfHy/rzH4WyVegBTGOR8O3dF9dxMyIA gvXLL2th20uL2ZTIC9sLphMDThnlVXuGTrPAcecYE4FtJ5LyK/+1nEvCk0IDDGiY n62BDBreSaQGq3Y4//5SxIPYq3+rfYptMChRlbMWwvFVVoa/9Xw= =r6q0 -----END PGP SIGNATURE----- -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
--- End Message ---
