Ubuntu
valgrind package

  1. Bug #1799696
  2. Comment #4

Comment 4 for bug 1799696

Revision history for this message
Dimitri John Ledkov (xnox) wrote :

A basic valgrind trace does not appear to be working in qemu-kvm VM anymore in disco-proposed:

autopkgtest [00:46:19]: test command1: valgrind /bin/true
autopkgtest [00:46:19]: test command1: [-----------------------
==1206== Memcheck, a memory error detector
==1206== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==1206== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info
==1206== Command: /bin/true
==1206==
==1206== Emulation fatal error -- Valgrind cannot continue:
==1206== Encountered an instruction that requires the vector facility.
==1206== That facility is not available on this host
==1206== at 0x4015980: _dl_runtime_resolve_vx (dl-trampoline.h:82)
==1206== by 0x482960D: ??? (in /usr/lib/s390x-linux-gnu/valgrind/vgpreload_core-s390x-linux.so)
==1206==
==1206== Valgrind has to exit now. Sorry.
==1206==

I will check the cpu settings that we use in these VMs, and/or if anything needs to be adjusted on the LPARs. Ideally I was expecting /bin/true, and valgrind /bin/true to just work on zEC12 and up; with or without vector instructions in Qemu KVM.