Package: valgrind
Version: 1:3.11.0-1+b1
Followup-For: Bug #823610

Seconding this bug. Currently valgrind'ing programs, that use
libgcrypt will fail with the program (incorrectly) receiving a SIGILL:

=== Cut ===
vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xC7 0xF0 0x72 0x4 0xFF 
0xC9
vex amd64->IR:   REX=1 REX.W=1 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR:   VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=0F
vex amd64->IR:   PFX.66=0 PFX.F2=0 PFX.F3=0
==18634== valgrind: Unrecognised instruction at address 0x5101663.
==18634==    at 0x5101663: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x510176A: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x5101908: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x50FD33F: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x50FE12B: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x50FD254: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x5109677: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x50D16DD: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x50603D2: ??? (in /lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x504DD5D: gcry_pk_decrypt (in 
/lib/x86_64-linux-gnu/libgcrypt.so.20.1.0)
==18634==    by 0x404E9A: crypto_pk_libgcrypt_decrypt (crypto_libgcrypt.c:332)
==18634==    by 0x40330E: crypto_pk_decrypt (crypto.c:161)
==18634== Your program just tried to execute an instruction that Valgrind
==18634== did not recognise.  There are two possible reasons for this.
==18634== 1. Your program has a bug and erroneously jumped to a non-code
==18634==    location.  If you are running Memcheck and you just saw a
==18634==    warning about a bad jump, it's probably your program's fault.
==18634== 2. The instruction is legitimate but Valgrind doesn't handle it,
==18634==    i.e. it's Valgrind's fault.  If you think this is the case or
==18634==    you are not sure, please let us know and we'll try to fix it.
==18634== Either way, Valgrind will now raise a SIGILL signal which will
==18634== probably kill your program.
==18634== 
==18634== Process terminating with default action of signal 4 (SIGILL)
=== Cut ===

-- 
With best wishes
Dmitry


-- System Information:
Debian Release: stretch/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages valgrind depends on:
ii  libc6      2.22-7
ii  libc6-dbg  2.22-7

Versions of packages valgrind recommends:
ii  gdb           7.10-1+b1
ii  valgrind-dbg  1:3.11.0-1+b1

Versions of packages valgrind suggests:
pn  alleyoop      <none>
pn  kcachegrind   <none>
pn  valgrind-mpi  <none>
pn  valkyrie      <none>

-- no debconf information

Reply via email to