- 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

- remove 32bit support for ALP

- add VEX-x86-pinsrd.patch (bko#276780)

- remove buildrequires on 32bit packages

- update filelist for 32bit disabled projects

  * More DWARF5 support as generated by clang14.
- drop unnecessary procps buildrequires
- add upstream handle-rseq-syscall.patch to fix run with glibc 2.35
  * 3.18.1 fixes a number of bugs and adds support for glibc-2.34, and for new
    platforms x86/FreeBSD and amd64/FreeBSD. Debuginfo reading is faster, and
    completed, and some newer ARM64 and S390 instructions are also supported.
- add s390x-z14-vector-support.patch (bsc#1180511)

• Files Changed
• Browse Source

- use boolean / extended requires for glibc requires

- 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

• Files Changed
• Browse Source

initialize package

• Browse Source