-
valgrind (1:3.18.1-1ubuntu2) jammy; urgency=medium
* d/patches/0001-Implement-linux-rseq-syscall-as-ENOSYS.patch: backport from
upstream to handle new syscall now used by glibc 2.35.
-- Michael Hudson-Doyle <email address hidden> Tue, 08 Feb 2022 12:40:42 +1300
-
valgrind (1:3.18.1-1ubuntu1) jammy; urgency=medium
* Merge with Debian; remaining changes:
- Lower over-inflated valgrind-dbg Recommends to Suggests instead.
- Don't strip vgpreload* on ARM; this results in unusable stack traces
without valgrind-dbg.
- Configure with --enable-only64bit on AArch64.
- Enable parallel builds.
- debian/patches/armv7-illegal-opcode.patch: fix a crash due to an
unhandled thumb instruction on armhf.
- debian/rules: use dh_missing --fail-missing to we don't overlook not
install files
- Add powerpc fixes. LP: #1916749
- LTO triggers undefined symbols in valgrind. Valgrind has a --enable-lto
configure time option, but that doesn't seem to help.
Disable LTO for now.
valgrind (1:3.18.1-1) unstable; urgency=medium
* New upstream release
- Add support for close_range syscall (Closes: #996743)
* Update d/copyright for renamed file
* Bump Standards-Version to 4.6.0 (no changes needed)
valgrind (1:3.17.0-1) unstable; urgency=medium
* New upstream release (Closes: #989691)
* Drop 12_drop-MPI-1-support.patch (fixed upstream)
* Drop 14_fix-debuginfo-section-duplicates-a-section-in-the-main-ELF-file.patch (merged upstream)
* Refresh patches
* Tools are now installed under libexec
* Avoid removing old bash completion file in mainscript
* Avoid marking files executable unnecessarily
-- Matthias Klose <email address hidden> Mon, 17 Jan 2022 12:04:17 +0100
-
valgrind (1:3.17.0-0ubuntu3) impish; urgency=medium
* d/patches0001-Update-helgrind-and-drd-suppression-libc-and-libpthr.patch,
d/patches0002-m_debuginfo-debuginfo.c-VG_-get_fnname_kind-_start-i.patch,
d/patches0003-Generate-a-ENOSYS-sys_ni_syscall-for-clone3-on-all-l.patch,
d/patches0004-unhandled-ppc64le-linux-syscall-252-statfs64-and-253.patch:
Backport patches from upstream to improve behaviour with glibc 2.34.
-- Michael Hudson-Doyle <email address hidden> Mon, 06 Sep 2021 20:56:30 +1200