Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
Name: valgrind-client-headers | Distribution: openSUSE Tumbleweed |
Version: 3.23.0 | Vendor: openSUSE |
Release: 1.1 | Build date: Sun Apr 28 17:47:13 2024 |
Group: Development/Tools/Debuggers | Build host: reproducible |
Size: 513519 | Source RPM: valgrind-client-headers-source-3.23.0-1.1.src.rpm |
Packager: https://bugs.opensuse.org | |
Url: https://valgrind.org/ | |
Summary: Header files for for Valgrind |
This package contains the BSD-style licensed Valgrind header files for inclusion into regular programs. The program can detect if it is running under Valgrind and interact with the Valgrind core and plugins.
GFDL-1.2-only AND GPL-2.0-or-later
* Sun Apr 28 2024 Dirk Müller <dmueller@suse.com> - update to 3.23.0: * 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 Andreas Schwab <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 Dirk Müller <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 Dirk Müller <dmueller@suse.com> - remove 32bit support for ALP * Tue Nov 14 2023 Dirk Müller <dmueller@suse.com> - add VEX-x86-pinsrd.patch (bko#276780) * Wed Oct 25 2023 Dirk Müller <dmueller@suse.com> - remove buildrequires on 32bit packages * Mon Oct 23 2023 Dirk Müller <dmueller@suse.com> - update filelist for 32bit disabled projects * Mon Aug 07 2023 Dirk Müller <dmueller@suse.com> - use boolean / extended requires for glibc requires * Thu May 18 2023 Dirk Müller <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) * Wed Mar 29 2023 Fabian Vogt <fvogt@suse.com> - Build without -z now (bsc#1208407) * Wed Oct 26 2022 Dirk Müller <dmueller@suse.com> - update to 3.20.0: * The option "--vgdb-stop-at=event1,event2,..." accepts the new value abexit. This indicates to invoke gdbserver when your program exits abnormally (i.e. with a non zero exit code). * Fix Rust v0 name demangling. * The Linux rseq syscall is now implemented as (silently) returning ENOSYS. * Add FreeBSD syscall wrappers for __specialfd and __realpathat. * Remove FreeBSD dependencies on COMPAT10, which fixes compatibility with HardenedBSD * The option --enable-debuginfod=<no|yes> [default: yes] has been added on Linux. * More DWARF5 support as generated by clang14. * Wed Aug 03 2022 Dirk Müller <dmueller@suse.com> - exclude client-headers from building for non-supported architectures * Wed Apr 20 2022 Adam Majer <adam.majer@suse.de> - fix build on SLE12 * Wed Apr 13 2022 Dirk Müller <dmueller@suse.com> - spec-cleaner suggested cleanups - drop unnecessary procps buildrequires * Tue Apr 12 2022 Dirk Müller <dmueller@suse.com> - update to 3.19.0 (bsc#1204685): * obsoletes backport 0001-arm64-Mismatch-detected-between-RDMA-and-atomics-fea.patch on older distributions * Fix Rust v0 name demangling. * The Linux rseq syscall is now implemented as (silently) returning ENOSYS. * Add FreeBSD syscall wrappers for __specialfd and __realpathat. * Remove FreeBSD dependencies on COMPAT10, which fixes compatibility with HardenedBSD * see https://valgrind.org/docs/manual/dist.news.html for list of bugfixes - drop handle-rseq-syscall.patch: upstream * Wed Mar 09 2022 Dirk Müller <dmueller@suse.com> - add upstream handle-rseq-syscall.patch to fix run with glibc 2.35 * Tue Nov 09 2021 Chris Bradbury <viff3000@gmail.com> - update to 3.18.1 (jsc#SLE-18639): * 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 Rust demangling has been improved. For PPC64, ISA 3.1 support has been completed, and some newer ARM64 and S390 instructions are also supported. * Sat Mar 20 2021 Dirk Müller <dmueller@suse.com> - update to 3.17.0 (jsc#SLE-18713): * 3.17.0 fixes a number of bugs and adds some functional changes: support for GCC 11, Clang 11, DWARF5 debuginfo, the 'debuginfod' debuginfo server, and some new instructions for Arm64, S390 and POWER. There are also some tool updates. - drop s390x-z14-vector-support.patch 0001-lmw-lswi-and-related-PowerPC-insns-aren-t-allowed-on.patch: upstream * Mon Jan 11 2021 Dirk Müller <dmueller@suse.com> - add 0001-lmw-lswi-and-related-PowerPC-insns-aren-t-allowed-on.patch (bsc#1180412) * Mon Jan 04 2021 Dirk Müller <dmueller@suse.com> - add s390x-z14-vector-support.patch (bsc#1180511)
/usr/include/valgrind /usr/include/valgrind/cachegrind.h /usr/include/valgrind/callgrind.h /usr/include/valgrind/dhat.h /usr/include/valgrind/drd.h /usr/include/valgrind/helgrind.h /usr/include/valgrind/memcheck.h /usr/include/valgrind/valgrind.h
Generated by rpm2html 1.8.1
Fabrice Bellet, Wed Nov 6 23:52:08 2024