Package Release Info

valgrind-3.24.0-160000.2.2

Update Info: Base Release
Available in Package Hub : 16.0

platforms

AArch64
ppc64le
s390x
x86-64

subpackages

valgrind-32bit

Change Logs

* Thu Jan 30 2025 dmueller@suse.com
- update to 3.24.0 (jsc#PED-10260):
  * Bad file descriptor usage now generates a real error with
  - -track-fds=yes that is suppressible and shows up in the
    xml output with full execution backtrace. The warnings
    shown without using the option are deprecated and will be
    removed in a future valgrind version.
  * Ada name demangling is now supported in error messages.
- Bugs fixed:
  * 202770  open fd at exit --log-socket=127.0.0.1:1500 with
  - -track-fds=yes
  * 276780  An instruction in fftw (Fast Fourier Transform) is
    unhandled by valgrind: vex x86->IR: unhandled instruction bytes:
    0x66 0xF 0x3A 0x2
  * 311655  --log-file=FILE leads to apparent fd leak
  * 317127  Fedora18/x86_64 --sanity-level=3 : aspacem segment
    mismatch
  * 337388  fcntl works on Valgrind's own file descriptors
  * 377966  arm64 unhandled instruction dc zva392146  aarch64:
    unhandled instruction 0xD5380001 (MRS rT, midr_el1)
  * 391148  Unhandled AVX instruction vmovq %xmm9,%xmm1
  * 392146  aarch64: unhandled instruction 0xD5380001 (MRS rT,
    midr_el1)
  * 412377  SIGILL on cache flushes on arm64
  * 417572  vex amd64->IR: unhandled instruction bytes: 0xC5 0x79
    0xD6 0xED 0xC5
  * 440180  s390x: Failed assertion in disassembler
  * 444781  MIPS: wrong syscall numbers used
  * 447989  Support Armv8.2 SHA-512 instructions
  * 445235  Java/Ada/D demangling is probably broken
  * 453044  gbserver_tests failures in aarch64
  * 479661  Valgrind leaks file descriptors
  * 486180  [Valgrind][MIPS] 'VexGuestArchState' has no member
    named 'guest_IP_AT_SYSCALL'
  * 486293  memccpy false positives
  * 486569  linux inotify_init syscall wrapper missing POST entry
    in syscall_table
  * 487439  SIGILL in JDK11, JDK17
  * 487993  Alignment error when using Eigen with Valgrind and
  - m32
  * 488026  Use of `sizeof` instead of `strlen
  * 488379  --track-fds=yes errors that cannot be suppressed with
  - -xml-file=
  * 488441  Add tests for --track-fds=yes --xml=yes and fd
    suppression tests
  * 489040  massif trace change to show the location increasing
    the stack
  * 489088  Valgrind throws unhandled instruction bytes: 0xC5
    0x79 0xD6 0xE0 0xC5
  * 489338  arm64: Instruction fcvtas should round 322.5 to 323,
    but result is 322.
  * 489676  vgdb handle EINTR and EAGAIN more consistently
  * 490651  Stop using -flto-partition=one
  * 491394  (vgModuleLocal_addDiCfSI): Assertion
    'di->fsm.have_rx_map &&
  * di->fsm.rw_map_count' failed
  * 492210  False positive on x86/amd64 with ZF taken directly
    from addition
  * 492214  statx(fd, NULL, AT_EMPTY_PATH) is supported since
    Linux 6.11
  * but not supported in valgrind
  * 492422  Please support DRM_IOCTL_SYNCOBJ_HANDLE_TO_FD
  * 492663  Valgrind ignores debug info for some binaries
  * 493418  Add bad fd usage errors for --track-fds in
    ML_(fd_allowed)
  * 493454  Missing FUSE_COMPATIBLE_MAY_BLOCK markers
  * 493507  direct readlink syscall from PRE handler is
    incompatible with FUSE_COMPATIBLE_MAY_BLOCK
  * 493959  s390x: Fix regtest failure for none/tests/s390x/op00
  * 493970  s390x: Store/restore FPC upon helper call causes
    slowdown
  * 494252  s390x: incorrect disassembly for LOCHI and friends
  * 494960  Fixes and tweaks for gsl19test
  * 495278  PowerPC instruction dcbf should allow the L field
    values of 4, 6 on ISA 3.0 and earlier, just ignore
    the value
  * 495469  aligned_alloc and posix_memalign missing MALLOC_TRACE
    with returned pointer
  * 495470  s390x: 3.24.0.RC1 missing file and regtest failure
- parallel-lto.patch: drop, obsolete
* Sun Apr 28 2024 dmueller@suse.com
- update to 3.23.0 (jsc#PED-10260):
  * Added ARM64 support for FreeBSD.
  * ARM64 now supports dotprod instructions (sdot/udot).
  * AMD64 better supports code build with -march=x86-64-v3.
    fused-multiple-add instructions (fma) are now emulated more
    accurately. And memcheck now handles __builtin_strcmp using 128/256
    bit vectors with sse4.1, avx/avx2.
  * S390X added support for NNPA (neural network processing assist)
    facility vector instructions VCNF, VCLFNH, VCFN, VCLFNL, VCRNF and
    NNPA (z16/arch14).
  * X86 recognizes new binutils-2.42 nop patterns.
- drop VEX-x86-nop-pattern.patch (upstream)
- drop armv6-support.diff (obsolete)
* Mon Feb 05 2024 schwab@suse.de
- VEX-x86-nop-pattern.patch: bko#478624 - Valgrind incompatibility with
  binutils-2.42 on x86 with new nop patterns (unhandled instruction bytes:
  0x2E 0x8D 0xB4 0x26)
* Fri Nov 24 2023 dmueller@suse.com
- update to 3.22.0: (jsc#PED-5442):
  * Memcheck now tests and warns about the values used for
    alignment and size. These apply to various functions: memalign,
    posix_memalign and aligned_alloc in C and various overloads
    of operators new and delete in C++. The kinds of error that can
    be detected are
  - invalid alignment, for instance the alignment is usually required
    to be a power of 2
  - mismatched alignment between aligned allocation and aligned
    deallocation
  - mismatched size when sized delete is used
  - bad size for functions that have implementation defined behaviour
    when the requested size is zero
  * many bug fixes, see https://valgrind.org/docs/manual/dist.news.html
* Wed Nov 15 2023 dmueller@suse.com
- remove 32bit support for ALP
* Tue Nov 14 2023 dmueller@suse.com
- add VEX-x86-pinsrd.patch (bko#276780)
* Wed Oct 25 2023 dmueller@suse.com
- remove buildrequires on 32bit packages
* Mon Oct 23 2023 dmueller@suse.com
- update filelist for 32bit disabled projects
* Mon Aug 07 2023 dmueller@suse.com
- use boolean / extended requires for glibc requires
* Thu May 18 2023 dmueller@suse.com
- update to 3.21.0:
  * When GDB is used to debug a program running under valgrind
    using the valgrind gdbserver, GDB will automatically load some
    python code provided in valgrind defining GDB front end
    commands corresponding to the valgrind monitor commands.
  * These GDB front end commands accept the same format as
    the monitor commands directly sent to the Valgrind
    gdbserver.
    These GDB front end commands provide a better integration
    in the GDB command line interface, so as to use for example
    GDB auto-completion, command specific help, searching for
    a command or command help matching a regexp, ...
    For relevant monitor commands, GDB will evaluate arguments
    to make the use of monitor commands easier.
    For example, instead of having to print the address of a
    variable to pass it to a subsequent monitor command, the
    GDB front end command will evaluate the address argument.
  * The vgdb utility now supports extended-remote protocol when
    invoked with --multi. In this mode the GDB run command is
    supported. Which means you don't need to run gdb and
    valgrind from different terminals.
  * The behaviour of realloc with a size of zero can now
    be changed for tools that intercept malloc. Those
    tools are memcheck, helgrind, drd, massif and dhat.
    Realloc implementations generally do one of two things
  - free the memory like free() and return NULL
    (GNU libc and ptmalloc).
  - either free the memory and then allocate a
    minimum sized block or just return the
    original pointer. Return NULL if the
    allocation of the minimum sized block fails
    (jemalloc, musl, snmalloc, Solaris, macOS).
  * When Valgrind is configured and built it will
    try to match the OS and libc behaviour. However
    if you are using a non-default library to replace
    malloc and family (e.g., musl on a glibc Linux or
    tcmalloc on FreeBSD) then you can use a command line
    option to change the behaviour of Valgrind:
  - -realloc-zero-bytes-frees=yes|no [yes on Linux glibc, no
    otherwise]
  * ==================== FIXED BUGS ====================
  * 241072  List tools in --help output
  * 327548  false positive while destroying mutex
  * 382034  Testcases build fixes for musl
  * 351857  confusing error message about valid command line
    option
  * 374596  inconsistent RDTSCP support on x86_64
  * 392331  Spurious lock not held error from inside
    pthread_cond_timedwait
  * 397083  Likely false positive "uninitialised value(s)" for
    __wmemchr_avx2 and __wmemcmp_avx2_movbe
  * 400793  pthread_rwlock_timedwrlock false positive
  * 419054  Unhandled syscall getcpu on arm32
  * 433873  openat2 syscall unimplemented on Linux
  * 434057  Add stdio mode to valgrind's gdbserver
  * 435441  valgrind fails to interpose malloc on musl 1.2.2 due
    to weak symbol name and no libc soname
  * 436413  Warn about realloc of size zero
  * 439685  compiler warning in callgrind/main.c
  * 444110  priv/guest_ppc_toIR.c:36198:31: warning: duplicated
    'if' condition.
  * 444487  hginfo test detects an extra lock inside data symbol
    "_rtld_local"
  * 444488  Use glibc.pthread.stack_cache_size tunable
  * 444568  drd/tests/pth_barrier_thr_cr fails on Fedora 38
  * 445743  "The impossible happened: mutex is locked
    simultaneously by two threads"
  * while using mutexes with priority inheritance and
    signals
  * 449309  Missing loopback device ioctl(s)
  * 459476  vgdb: allow address reuse to avoid "address already
    in use" errorsuse" errors
  * 460356  s390: Sqrt32Fx4 -- cannot reduce tree
  * 462830  WARNING: unhandled amd64-freebsd syscall: 474
  * 463027  broken check for MPX instruction support in assembler
  * 464103  Enhancement: add a client request to DHAT to mark
    memory to be histogrammed
  * 464476  Firefox fails to start under Valgrind
  * 464609  Valgrind memcheck should support Linux pidfd_open
  * 464680  Show issues caused by memory policies like selinux
    deny_execmem
  * 464859  Build failures with GCC-13 (drd tsan_unittest)
  * 464969  D language demangling
  * 465435  m_libcfile.c:66 (vgPlain_safe_fd): Assertion 'newfd
    >= VG_(fd_hard_limit)' failed.
  * 466104  aligned_alloc problems, part 1
  * 467036  Add time cost statistics for Regtest
  * 467482  Build failure on aarch64 Alpine
  * 467714  fdleak_* and rlimit tests fail when parent process
    has more than
  * 64 descriptors opened
  * 467839  Gdbserver: Improve compatibility of library directory
    name
  * 468401  [PATCH] Add a style file for clang-format
  * 468556  Build failure for vgdb
  * 468606  build: remove "Valgrind relies on GCC" check/output
  * 469097  ppc64(be) doesn't support SCV syscall instruction
  * n-i-bz  FreeBSD rfork syscall fail with EINVAL or ENOSYS
    rather than VG_(unimplemented)
- disable LTO on ppc64 (bsc#1205923)