pool/valgrind
SHA256
2
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

- update to 3.16.0:

Browse Source 
* Many bugfixes, too many to list here, see NEWS file
  - The implicit memcpy done by each call to realloc now counts towards the
    read and write counts of resized heap blocks, making those counts higher
    and more accurate.
  - cg_annotate's --auto and --show-percs options now default to 'yes', because
    they are usually wanted.
  - callgrind_annotate's --auto and --show-percs options now default to 'yes',
    because they are usually wanted.
  - The command option --collect-systime has been enhanced to specify
    the unit used to record the elapsed time spent during system calls.
    The command option now accepts the values no|yes|msec|usec|nsec,
    where yes is a synonym of msec.  When giving the value nsec, the
    system cpu time of system calls is also recorded.
  - Several memcheck options are now dynamically changeable.
    Use  valgrind --help-dyn-options  to list them.
  - The release 3.15 introduced a backward incompatible change for
    some suppression entries related to preadv and pwritev syscalls.
    When reading a suppression entry using the unsupported 3.14 format,
    valgrind will now produce a warning to say the suppression entry will not
    work, and suggest the needed change.
  - Significantly fewer false positive errors on optimised code generated by
    Clang and GCC.  In particular, Memcheck now deals better with the
    situation where the compiler will transform C-level "A && B" into "B && A"
    under certain circumstances (in which the transformation is valid).
    Handling of integer equality/non-equality checks on partially defined
    values is also improved on some architectures.
  - The exprimental Stack and Global Array Checking tool has been removed.
    It only ever worked on x86 and amd64, and even on those it had a
    high false positive rate and was slow.  An alternative for detecting

OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=221
This commit is contained in:
Dirk Mueller 2020-06-19 15:21:22 +00:00 committed by Git OBS Bridge
parent 61511806cd
commit a306f3d4aa
6 changed files with 2473 additions and 2249 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

34
0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch Normal file
View File

@ -0,0 +1,34 @@
From fb6f7abcbc92506d302fb18a2c5fc853d2929248 Mon Sep 17 00:00:00 2001
From: Carl Love <cel@us.ibm.com>
Date: Tue, 9 Jun 2020 10:42:03 -0500
Subject: [PATCH] Power PC Fix extraction of the L field for sync instruction
The L field is currently a two bit[22:21] field in ISA 3.0. The size of the
L field has changed over time.
Currently the ISA 3.0 Valgrind sync instruction support code sets the
flag_L for the instruction L field to a five bit value that includes bits
that are marked reserved the sync instruction. This patch fixes the issue for ISA 3.0
to only setting flag_L the specified two bits.
Valgrind bugzilla: https://bugs.kde.org/show_bug.cgi?id=422677
---
VEX/priv/guest_ppc_toIR.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/VEX/priv/guest_ppc_toIR.c b/VEX/priv/guest_ppc_toIR.c
index 582c59ec0..c4965a19e 100644
--- a/VEX/priv/guest_ppc_toIR.c
+++ b/VEX/priv/guest_ppc_toIR.c
@@ -8777,7 +8777,7 @@ static Bool dis_memsync ( UInt theInstr )
/* X-Form, XL-Form */
UChar opc1 = ifieldOPC(theInstr);
UInt b11to25 = IFIELD(theInstr, 11, 15);
- UChar flag_L = ifieldRegDS(theInstr);
+ UChar flag_L = IFIELD(theInstr, 21, 2); //ISA 3.0
UInt b11to20 = IFIELD(theInstr, 11, 10);
UInt M0 = IFIELD(theInstr, 11, 5);
UChar rD_addr = ifieldRegDS(theInstr);
--
2.27.0

3
valgrind-3.15.0.tar.bz2
View File

@ -1,3 +0,0 @@
version https://git-lfs.github.com/spec/v1
oid sha256:417c7a9da8f60dd05698b3a7bc6002e4ef996f14c13f0ff96679a16873e78ab1
size 20241437

3
valgrind-3.16.0.tar.bz2 Normal file
View File

@ -0,0 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:582d5127ba56dfeaab4c6ced92a742b2921148e28a5d55055aedd8f75f1cf633
size 16267317

50
valgrind.changes
View File

@ -1,3 +1,53 @@
-------------------------------------------------------------------
Fri Jun 19 07:55:22 UTC 2020 - Dirk Mueller <dmueller@suse.com>
- update to 3.16.0:
* Many bugfixes, too many to list here, see NEWS file
- The implicit memcpy done by each call to realloc now counts towards the
read and write counts of resized heap blocks, making those counts higher
and more accurate.
- cg_annotate's --auto and --show-percs options now default to 'yes', because
they are usually wanted.
- callgrind_annotate's --auto and --show-percs options now default to 'yes',
because they are usually wanted.
- The command option --collect-systime has been enhanced to specify
the unit used to record the elapsed time spent during system calls.
The command option now accepts the values no|yes|msec|usec|nsec,
where yes is a synonym of msec. When giving the value nsec, the
system cpu time of system calls is also recorded.
- Several memcheck options are now dynamically changeable.
Use valgrind --help-dyn-options to list them.
- The release 3.15 introduced a backward incompatible change for
some suppression entries related to preadv and pwritev syscalls.
When reading a suppression entry using the unsupported 3.14 format,
valgrind will now produce a warning to say the suppression entry will not
work, and suggest the needed change.
- Significantly fewer false positive errors on optimised code generated by
Clang and GCC. In particular, Memcheck now deals better with the
situation where the compiler will transform C-level "A && B" into "B && A"
under certain circumstances (in which the transformation is valid).
Handling of integer equality/non-equality checks on partially defined
values is also improved on some architectures.
- The exprimental Stack and Global Array Checking tool has been removed.
It only ever worked on x86 and amd64, and even on those it had a
high false positive rate and was slow. An alternative for detecting
stack and global array overruns is using the AddressSanitizer (ASAN)
facility of the GCC and Clang compilers, which require you to rebuild
your code with -fsanitize=address.
- Option -T tells vgdb to output a timestamp in the vgdb information messages.
- The gdbserver monitor commands that require an address and an optional
length argument now accepts the alternate 'C like' syntax "address[length]".
For example, the memcheck command "monitor who_points_at 0x12345678 120"
can now also be given as "monitor who_points_at 0x12345678[120]".
- 001-Add-newer-constants-for-prctl-syscall.patch
0001-Fix-makefile-consistency-check.patch
0001-s390x-Add-CPU-model-for-z15.patch
0001-s390x-Add-models-z14-and-z14-ZR1.patch
0001-s390x-Clean-up-s390-check-opcodes.pl.patch
0002-Add-support-for-PR_CAPBSET_READ-and-_DROP-syscalls.patch:
dropped upstream.
- add 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch (bsc#1173135)
-------------------------------------------------------------------
Mon May 11 12:14:25 UTC 2020 - Dirk Mueller <dmueller@suse.com>

19
valgrind.spec
View File

@ -29,7 +29,7 @@
%bcond_without docs
Name: valgrind%{?psuffix}
Version: 3.15.0
Version: 3.16.0
Release: 0
Summary: Memory Management Debugger
License: GPL-2.0-or-later AND GFDL-1.2-only
@ -39,15 +39,9 @@ Source0: ftp://sourceware.org/pub/valgrind/valgrind-%{version}.tar.bz2
# https://bugs.kde.org/show_bug.cgi?id=390553
# https://github.com/olafhering/valgrind/compare/olh-base-master...olh-fixes-master
Patch0: valgrind.xen.patch
# PATCH-FIX-UPSTREAM 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch
Patch1: 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch
Patch2: armv6-support.diff
# PATCH-FIX-UPSTREAM
Patch3: 0001-Add-newer-constants-for-prctl-syscall.patch
# PATCH-FIX-UPSTREAM
Patch4: 0002-Add-support-for-PR_CAPBSET_READ-and-_DROP-syscalls.patch
Patch5: 0001-Fix-makefile-consistency-check.patch
Patch6: 0001-s390x-Add-models-z14-and-z14-ZR1.patch
Patch7: 0001-s390x-Clean-up-s390-check-opcodes.pl.patch
Patch8: 0001-s390x-Add-CPU-model-for-z15.patch
Patch9: parallel-lto.patch
Patch10: dhat-use-datadir.patch
%if "%{flavor}" == ""
@ -159,13 +153,8 @@ but it has been successfully used to optimize several KDE applications.
%prep
%setup -q -n valgrind-%{version}
%patch0 -p1
%patch1 -p1
%patch2
%patch3 -p1
%patch4 -p1
%patch5 -p1
%patch6 -p1
%patch7 -p1
%patch8 -p1
%patch9 -p1
%patch10 -p1

4613
valgrind.xen.patch
View File

File diff suppressed because it is too large Load Diff