| Index | index by Group | index by Distribution | index by Vendor | index by creation date | index by Name | Mirrors | Help | Search |
| Name: valgrind | Distribution: SUSE Linux Enterprise 15 |
| Version: 3.22.0 | Vendor: SUSE LLC <https://www.suse.com/> |
| Release: 150600.1.3 | Build date: Thu May 9 14:34:01 2024 |
| Group: Development/Tools/Debuggers | Build host: s390zp31 |
| Size: 30145812 | Source RPM: valgrind-3.22.0-150600.1.3.src.rpm |
| Packager: https://www.suse.com/ | |
| Url: https://valgrind.org/ | |
| Summary: Memory Management Debugger | |
Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.
GFDL-1.2-only AND GPL-2.0-or-later
* 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)
* Wed Mar 29 2023 fvogt@suse.com
- Build without -z now (bsc#1208407)
* Wed Oct 26 2022 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 dmueller@suse.com
- exclude client-headers from building for non-supported architectures
* Wed Apr 20 2022 adam.majer@suse.de
- fix build on SLE12
* Wed Apr 13 2022 dmueller@suse.com
- spec-cleaner suggested cleanups
- drop unnecessary procps buildrequires
* Tue Apr 12 2022 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 dmueller@suse.com
- add upstream handle-rseq-syscall.patch to fix run with glibc 2.35
* Tue Nov 09 2021 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 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 dmueller@suse.com
- add 0001-lmw-lswi-and-related-PowerPC-insns-aren-t-allowed-on.patch (bsc#1180412)
* Mon Jan 04 2021 dmueller@suse.com
- add s390x-z14-vector-support.patch (bsc#1180511)
* Sun Aug 16 2020 dmueller@suse.com
- update to 3.16.1 (jsc#SLE-13769):
* PPC sync instruction L field should only be 2 bits in ISA 3.0
* vex: the `impossible' happened: expr_is_guardable: unhandled expr
- remove 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch (upstream)
* Fri Jun 19 2020 msuchanek@suse.de
- Use autopatch
- Change armv6-support.diff to a/b format
* Fri Jun 19 2020 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
0001-Add-newer-constants-for-prctl-syscall.patch
0002-Add-support-for-PR_CAPBSET_READ-and-_DROP-syscalls.patch:
dropped as those patches were from upstream and are already in 3.16.0
- add 0001-Power-PC-Fix-extraction-of-the-L-field-for-sync-inst.patch (bsc#1173135)
* Mon May 11 2020 dmueller@suse.com
- add dhat-use-datadir.patch:
* move the dhat* scripts to datadir
* Wed Mar 25 2020 mliska@suse.cz
- Add parallel-lto.patch in order to make LTO LTRANS phase
parallel. It will significantly improve build time.
* Thu Mar 12 2020 dmueller@suse.com
- add 0001-Fix-makefile-consistency-check.patch
0001-s390x-Add-models-z14-and-z14-ZR1.patch
0001-s390x-Clean-up-s390-check-opcodes.pl.patch
0001-s390x-Add-CPU-model-for-z15.patch (bsc#1165834)
* Tue Jan 28 2020 guillaume.gardet@opensuse.org
- Disable %check on %arm as it never passed - boo#1130395
* Sun Jan 19 2020 stefan.bruens@rwth-aachen.de
- Add support for PR_CAPBSET_READ/DROP syscalls. Fixes false
error messages with latest libcap 2.30.
* 0001-Add-newer-constants-for-prctl-syscall.patch
* 0002-Add-support-for-PR_CAPBSET_READ-and-_DROP-syscalls.patch
* Wed Nov 27 2019 dmueller@suse.com
- remove jit-register-unregister.diff (fails patch not applied check)
* Tue Oct 29 2019 dmueller@suse.com
- move s390-*xml files to main package (bsc#1147071)
* Tue Oct 22 2019 stefan.bruens@rwth-aachen.de
- Use _multibuild for creating the client-headers subpackage. As
the headers are just copied over, the package has no substantial
build dependencies.
* Thu Oct 17 2019 stefan.bruens@rwth-aachen.de
- Move the BSD-style licensed client headers to a subpackage.
Packages only requiring e.g. valgrind.h during build no longer
need the full valgrind and valgrind-devel packages then.
- Clean up documentation a bit:
+ use %build_cond, drop unused docbook_4 BuildRequires
+ remove the Postscript Valgrind manual in favor of the PDF one.
- Add GFDL-1.2 to the License, relevant for man pages and Valgrind
PDF/HTML manual.
* Wed May 08 2019 dmueller@suse.com
- update to 3.15.0 (fate#327402) (jira SLE-5861):
3.15.0 is a feature release with many improvements and the usual collection of
bug fixes.
This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,
PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,
MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,
X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12. There is also preliminary
support for X86/macOS 10.13 and AMD64/macOS 10.13.
* ==================== CORE CHANGES ===================
* The XTree Massif output format now makes use of the information obtained
when specifying --read-inline-info=yes.
* amd64 (x86_64): the RDRAND and F16C insn set extensions are now supported.
* ==================== TOOL CHANGES ====================
* DHAT:
- DHAT been thoroughly overhauled, improved, and given a GUI. As a result,
it has been promoted from an experimental tool to a regular tool. Run it
with --tool=dhat instead of --tool=exp-dhat.
- DHAT now prints only minimal data when the program ends, instead writing
the bulk of the profiling data to a file. As a result, the --show-top-n
and --sort-by options have been removed.
- Profile results can be viewed with the new viewer, dh_view.html. When
a run ends, a short message is printed, explaining how to view the result.
- See the documentation for more details.
* Cachegrind:
- cg_annotate has a new option, --show-percs, which prints percentages next
to all event counts.
* Callgrind:
- callgrind_annotate has a new option, --show-percs, which prints percentages
next to all event counts.
- callgrind_annotate now inserts commas in call counts, and
sort the caller/callee lists in the call tree.
* Massif:
- The default value for --read-inline-info is now "yes" on
Linux/Android/Solaris. It is still "no" on other OS.
* Memcheck:
- The option --xtree-leak=yes (to output leak result in xtree format)
automatically activates the option --show-leak-kinds=all, as xtree
visualisation tools such as kcachegrind can in any case select what kind
of leak to visualise.
- There has been further work to avoid false positives. In particular,
integer equality on partially defined inputs (C == and !=) is now handled
better.
- remove 0001-Bug-385411-s390x-Add-z13-vector-floating-point-suppo.patch
0001-Bug-385411-s390x-Tests-and-internals-for-z13-vector-.patch
0001-Bug-397187-s390x-Add-vector-register-support-for-vgd.patch
0001-Bug-399444-s390x-Drop-unnecessary-check-in-s390_irge.patch
0001-Bug-400490-s390x-Fix-register-allocation-for-VRs-vs-.patch
0001-Bug-400491-s390x-Sign-extend-immediate-operand-of-LO.patch
0001-Bug-402519-POWER-3.0-addex-instruction-incorrectly-i.patch
0001-Bug-403552-s390x-Fix-vector-facility-bit-number.patch
0001-s390x-more-fixes.patch
Implement-emulated-system-registers.-Fixes-392146.patch (all upstream)
* Wed Apr 24 2019 mliska@suse.cz
- Disable LTO (boo#1133288).
* Tue Feb 19 2019 dmueller@suse.com
- add 0001-Bug-385411-s390x-Add-z13-vector-floating-point-suppo.patch
0001-Bug-385411-s390x-Tests-and-internals-for-z13-vector-.patch
0001-Bug-399444-s390x-Drop-unnecessary-check-in-s390_irge.patch
0001-Bug-403552-s390x-Fix-vector-facility-bit-number.patch (bsc#1124111)
* Sat Feb 09 2019 schwab@suse.de
- Don't package files twice on ppc64
* Wed Jan 16 2019 msuchanek@suse.de
- Fix POWER9 addex instruction emulation (bsc#1121025).
0001-Bug-402519-POWER-3.0-addex-instruction-incorrectly-i.patch
* Fri Jan 11 2019 dmueller@suse.com
- split into a -32bit subpackage, fix buildrequires for older distros
* Thu Dec 06 2018 bwiedemann@suse.com
- drop unreproducible unused .a files to make the package build
reproducible (boo#1118163)
* Sun Nov 25 2018 olaf@aepfle.de
- update valgrind.xen.patch to branch bug390553-20181125-ddfc274b2
* Thu Nov 22 2018 dmueller@suse.com
- build against Toolchain module for SLE12
- add 0001-Bug-397187-s390x-Add-vector-register-support-for-vgd.patch
0001-Bug-400490-s390x-Fix-register-allocation-for-VRs-vs-.patch,
0001-Bug-400491-s390x-Sign-extend-immediate-operand-of-LO.patch,
0001-s390x-more-fixes.patch,
Implement-emulated-system-registers.-Fixes-392146.patch (FATE#326355)
- enable check (poo#36751)
* Wed Nov 21 2018 dmueller@suse.com
- update to 3.14.0 (bsc#1114575, FATE#326355):
see http://www.valgrind.org/docs/manual/dist.news.html
* The new option --keep-debuginfo=no|yes (default no) can be used to retain
debug info for unloaded code. This allows saved stack traces (e.g. for
memory leaks) to include file/line info for code that has been dlclose'd (or
similar). See the user manual for more information and known limitations.
* Ability to specify suppressions based on source file name and line number.
* Majorly overhauled register allocator. No end-user changes, but the JIT
generates code a bit more quickly now.
* Preliminary support for macOS 10.13 has been added.
* mips: support for MIPS32/MIPS64 Revision 6 has been added.
* mips: support for MIPS SIMD architecture (MSA) has been added.
* mips: support for MIPS N32 ABI has been added.
* s390: partial support for vector instructions (integer and string) has been
added.
* Helgrind: Addition of a flag
- -delta-stacktrace=no|yes [yes on linux amd64/x86]
which specifies how full history stack traces should be computed.
Setting this to =yes can speed up Helgrind by 25% when using
- -history-level=full.
* Memcheck: reduced false positive rate for optimised code created by Clang 6
/ LLVM 6 on x86, amd64 and arm64. In particular, Memcheck analyses code
blocks more carefully to determine where it can avoid expensive definedness
checks without loss of precision. This is controlled by the flag
- -expensive-definedness-checks=no|auto|yes [auto].
* Valgrind is now buildable with link-time optimisation (LTO). A new
configure option --enable-lto=yes allows building Valgrind with LTO. If the
toolchain supports it, this produces a smaller/faster Valgrind (up to 10%).
Note that if you are doing Valgrind development, --enable-lto=yes massively
slows down the build process.
- remove epoll-wait-fix.patch,
Fix-access-to-time-base-register-to-return-64-bits.patch,
0001-Accept-read-only-PT_LOAD-segments-and-.rodata.patch (upstream),
* Tue Sep 25 2018 msuchanek@suse.com
- valgrind truncates powerpc timebase to 32-bits (bsc#1109589).
Fix-access-to-time-base-register-to-return-64-bits.patch
* Thu Sep 13 2018 dmueller@suse.com
- valgrind.xen.patch: refresh
* Tue Aug 28 2018 stefan.bruens@rwth-aachen.de
- Filter out -m64 from optflags, breaks build of 32 bit parts
- Cleanup, remove suse_version < 1100 conditionals
- Use %license for COPYING, COPYING.DOCS
* Mon Aug 27 2018 stefan.bruens@rwth-aachen.de
- Fix missing debuginfo with current binutils, boo#1103239
0001-Accept-read-only-PT_LOAD-segments-and-.rodata.patch
* Fri Jun 08 2018 mbrugger@suse.com
- ad Implement-emulated-system-registers.-Fixes-392146.patch (bsc#1086543)
* Thu Feb 22 2018 olaf@aepfle.de
- add valgrind.xen.patch to handle Xen 4.10 (fate#321394, fate#322686)
* Mon Oct 30 2017 dmueller@suse.com
- add epoll-wait-fix.patch (bsc#1064958)
* Sun Jun 25 2017 dmueller@suse.com
- update to 3.13.0 (fate#321455):
- remove fix-ppcl64-clobber-list.patch
3.13.0 is a feature release with many improvements and the
usual collection of bug fixes.
See http://valgrind.org/docs/manual/dist.news.html
* Tue Apr 25 2017 mliska@suse.cz
- Add fix-ppcl64-clobber-list.patch: fix clobber list on ppcl64le,
it's backport of upstream patch.
* Tue Dec 27 2016 foss@grueninger.de
- update to 3.12.0 (bsc#1017016, FATE#321455, bsc#987635, CVE-2016-6131)
* 3.12.0 is a feature release with many improvements and the usual
collection of bug fixes. The full changelog can be found at
http://valgrind.org/docs/manual/dist.news.html
or
/usr/share/doc/packages/valgrind/NEWS
- droped patches which are part of the release:
gcc5.patch, r15702.diff, r15792.diff, r15802.diff, svn-r15766.patch,
vex-r3197.diff, vex-r3210.diff, vex-r3213.diff
* Thu Oct 20 2016 stefan.bruens@rwth-aachen.de
- add vex-r3213.diff (kde#356393)
* Sat May 28 2016 dmueller@suse.com
- add vex-r3197.diff (bsc#981447)
* Wed Apr 20 2016 jslaby@suse.com
- The previous did not help, remove -strong first.
* Tue Apr 19 2016 meissner@suse.com
- also remove -fstack-protector-strong from the CFLAGS
* Fri Apr 01 2016 dmueller@suse.com
- add r15702.diff, r15792.diff, vex-r3210.diff, r15802.diff (fate#319608)
* Mon Feb 22 2016 schwab@suse.de
- glibc-version.patch: removed, no longer needed
* Mon Feb 15 2016 dmueller@suse.com
- update to 3.11.0 (fate#319608):
* 3.11.0 is a feature release with many improvements and the usual
collection of bug fixes.
- replace gcc-version.patch with gcc5.patch: This is the upstream
version
- drop valgrind-linux-4.0.patch: merged upstream
- add svn-r15766.patch: Fix valgrind with recent kernels
- jit-register-unregister.diff commented out, needs porting
* Thu Aug 06 2015 schwab@suse.de
- glibc-version.patch: Add support for glibc 2.22.
* Fri Apr 24 2015 dimstar@opensuse.org
- Add valgrind-linux-4.0.patch: Fix build with linux kernel 4.0+.
Taken from svn, rev 14955.
* Thu Apr 02 2015 mpluskal@suse.com
- Cleanup spec file with spec-cleaner
- Update to 3.10.1
* bugfix release (for full list of solved issues see NEWS file)
* Thu Feb 12 2015 rguenther@suse.com
- gcc-version.patch: Add support for GCC 5.
* Mon Feb 09 2015 schwab@suse.de
- glibc-version.patch: Add support for glibc 2.21.
/usr/bin/callgrind_annotate /usr/bin/callgrind_control /usr/bin/cg_annotate /usr/bin/cg_diff /usr/bin/cg_merge /usr/bin/ms_print /usr/bin/valgrind /usr/bin/valgrind-di-server /usr/bin/valgrind-listener /usr/bin/vgdb /usr/lib/valgrind /usr/lib/valgrind/64bit-avx-valgrind-s1.xml /usr/lib/valgrind/64bit-avx-valgrind-s2.xml /usr/lib/valgrind/64bit-avx.xml /usr/lib/valgrind/64bit-core-valgrind-s1.xml /usr/lib/valgrind/64bit-core-valgrind-s2.xml /usr/lib/valgrind/64bit-core.xml /usr/lib/valgrind/64bit-linux-valgrind-s1.xml /usr/lib/valgrind/64bit-linux-valgrind-s2.xml /usr/lib/valgrind/64bit-linux.xml /usr/lib/valgrind/64bit-sse-valgrind-s1.xml /usr/lib/valgrind/64bit-sse-valgrind-s2.xml /usr/lib/valgrind/64bit-sse.xml /usr/lib/valgrind/amd64-avx-coresse-valgrind.xml /usr/lib/valgrind/amd64-avx-coresse.xml /usr/lib/valgrind/amd64-avx-linux-valgrind.xml /usr/lib/valgrind/amd64-avx-linux.xml /usr/lib/valgrind/amd64-coresse-valgrind.xml /usr/lib/valgrind/amd64-linux-valgrind.xml /usr/lib/valgrind/cachegrind-s390x-linux /usr/lib/valgrind/callgrind-s390x-linux /usr/lib/valgrind/default.supp /usr/lib/valgrind/dhat-s390x-linux /usr/lib/valgrind/drd-s390x-linux /usr/lib/valgrind/exp-bbv-s390x-linux /usr/lib/valgrind/getoff-s390x-linux /usr/lib/valgrind/helgrind-s390x-linux /usr/lib/valgrind/lackey-s390x-linux /usr/lib/valgrind/massif-s390x-linux /usr/lib/valgrind/memcheck-s390x-linux /usr/lib/valgrind/mips64-cp0-valgrind-s1.xml /usr/lib/valgrind/mips64-cp0-valgrind-s2.xml /usr/lib/valgrind/mips64-cp0.xml /usr/lib/valgrind/mips64-cpu-valgrind-s1.xml /usr/lib/valgrind/mips64-cpu-valgrind-s2.xml /usr/lib/valgrind/mips64-cpu.xml /usr/lib/valgrind/mips64-fpu-valgrind-s1.xml /usr/lib/valgrind/mips64-fpu-valgrind-s2.xml /usr/lib/valgrind/mips64-fpu.xml /usr/lib/valgrind/mips64-linux-valgrind.xml /usr/lib/valgrind/mips64-linux.xml /usr/lib/valgrind/none-s390x-linux /usr/lib/valgrind/power-core-valgrind-s1.xml /usr/lib/valgrind/power-core-valgrind-s2.xml /usr/lib/valgrind/power64-core-valgrind-s1.xml /usr/lib/valgrind/power64-core-valgrind-s2.xml /usr/lib/valgrind/power64-core.xml /usr/lib/valgrind/power64-core2-valgrind-s1.xml /usr/lib/valgrind/power64-core2-valgrind-s2.xml /usr/lib/valgrind/power64-linux-valgrind-s1.xml /usr/lib/valgrind/power64-linux-valgrind-s2.xml /usr/lib/valgrind/power64-linux.xml /usr/lib/valgrind/s390-acr-valgrind-s1.xml /usr/lib/valgrind/s390-acr-valgrind-s2.xml /usr/lib/valgrind/s390-acr.xml /usr/lib/valgrind/s390-fpr-valgrind-s1.xml /usr/lib/valgrind/s390-fpr-valgrind-s2.xml /usr/lib/valgrind/s390-fpr.xml /usr/lib/valgrind/s390-vx-valgrind-s1.xml /usr/lib/valgrind/s390-vx-valgrind-s2.xml /usr/lib/valgrind/s390-vx.xml /usr/lib/valgrind/s390x-core64-valgrind-s1.xml /usr/lib/valgrind/s390x-core64-valgrind-s2.xml /usr/lib/valgrind/s390x-core64.xml /usr/lib/valgrind/s390x-generic-valgrind.xml /usr/lib/valgrind/s390x-generic.xml /usr/lib/valgrind/s390x-linux64-valgrind-s1.xml /usr/lib/valgrind/s390x-linux64-valgrind-s2.xml /usr/lib/valgrind/s390x-linux64.xml /usr/lib/valgrind/s390x-vx-linux-valgrind.xml /usr/lib/valgrind/s390x-vx-linux.xml /usr/lib/valgrind/valgrind-monitor-def.py /usr/lib/valgrind/valgrind-monitor.py /usr/lib/valgrind/vgpreload_core-s390x-linux.so /usr/lib/valgrind/vgpreload_dhat-s390x-linux.so /usr/lib/valgrind/vgpreload_drd-s390x-linux.so /usr/lib/valgrind/vgpreload_helgrind-s390x-linux.so /usr/lib/valgrind/vgpreload_massif-s390x-linux.so /usr/lib/valgrind/vgpreload_memcheck-s390x-linux.so /usr/share/doc/packages/valgrind /usr/share/doc/packages/valgrind/AUTHORS /usr/share/doc/packages/valgrind/NEWS /usr/share/doc/packages/valgrind/README /usr/share/doc/packages/valgrind/README.aarch64 /usr/share/doc/packages/valgrind/README.android /usr/share/doc/packages/valgrind/README.android_emulator /usr/share/doc/packages/valgrind/README.freebsd /usr/share/doc/packages/valgrind/README.mips /usr/share/doc/packages/valgrind/README.s390 /usr/share/doc/packages/valgrind/README.solaris /usr/share/doc/packages/valgrind/README_DEVELOPERS /usr/share/doc/packages/valgrind/README_DEVELOPERS_processes /usr/share/doc/packages/valgrind/README_MISSING_SYSCALL_OR_IOCTL /usr/share/doc/packages/valgrind/README_PACKAGERS /usr/share/doc/packages/valgrind/html /usr/share/doc/packages/valgrind/html/FAQ.html /usr/share/doc/packages/valgrind/html/QuickStart.html /usr/share/doc/packages/valgrind/html/bbv-manual.html /usr/share/doc/packages/valgrind/html/cg-manual.html /usr/share/doc/packages/valgrind/html/cl-format.html /usr/share/doc/packages/valgrind/html/cl-manual.html /usr/share/doc/packages/valgrind/html/design-impl.html /usr/share/doc/packages/valgrind/html/dh-manual.html /usr/share/doc/packages/valgrind/html/dist.authors.html /usr/share/doc/packages/valgrind/html/dist.html /usr/share/doc/packages/valgrind/html/dist.news.html /usr/share/doc/packages/valgrind/html/dist.news.old.html /usr/share/doc/packages/valgrind/html/dist.readme-android.html /usr/share/doc/packages/valgrind/html/dist.readme-android_emulator.html /usr/share/doc/packages/valgrind/html/dist.readme-developers.html /usr/share/doc/packages/valgrind/html/dist.readme-freebsd.html /usr/share/doc/packages/valgrind/html/dist.readme-mips.html /usr/share/doc/packages/valgrind/html/dist.readme-missing.html /usr/share/doc/packages/valgrind/html/dist.readme-packagers.html /usr/share/doc/packages/valgrind/html/dist.readme-s390.html /usr/share/doc/packages/valgrind/html/dist.readme-solaris.html /usr/share/doc/packages/valgrind/html/dist.readme.html /usr/share/doc/packages/valgrind/html/drd-manual.html /usr/share/doc/packages/valgrind/html/faq.html /usr/share/doc/packages/valgrind/html/hg-manual.html /usr/share/doc/packages/valgrind/html/images /usr/share/doc/packages/valgrind/html/images/dh-tree.png /usr/share/doc/packages/valgrind/html/images/home.png /usr/share/doc/packages/valgrind/html/images/kcachegrind_xtree.png /usr/share/doc/packages/valgrind/html/images/next.png /usr/share/doc/packages/valgrind/html/images/prev.png /usr/share/doc/packages/valgrind/html/images/up.png /usr/share/doc/packages/valgrind/html/index.html /usr/share/doc/packages/valgrind/html/license.gfdl.html /usr/share/doc/packages/valgrind/html/license.gpl.html /usr/share/doc/packages/valgrind/html/licenses.html /usr/share/doc/packages/valgrind/html/lk-manual.html /usr/share/doc/packages/valgrind/html/manual-core-adv.html /usr/share/doc/packages/valgrind/html/manual-core.html /usr/share/doc/packages/valgrind/html/manual-intro.html /usr/share/doc/packages/valgrind/html/manual-writing-tools.html /usr/share/doc/packages/valgrind/html/manual.html /usr/share/doc/packages/valgrind/html/mc-manual.html /usr/share/doc/packages/valgrind/html/ms-manual.html /usr/share/doc/packages/valgrind/html/nl-manual.html /usr/share/doc/packages/valgrind/html/quick-start.html /usr/share/doc/packages/valgrind/html/tech-docs.html /usr/share/doc/packages/valgrind/html/vg_basic.css /usr/share/doc/packages/valgrind/valgrind_manual.pdf /usr/share/licenses/valgrind /usr/share/licenses/valgrind/COPYING /usr/share/licenses/valgrind/COPYING.DOCS /usr/share/man/man1/callgrind_annotate.1.gz /usr/share/man/man1/callgrind_control.1.gz /usr/share/man/man1/cg_annotate.1.gz /usr/share/man/man1/cg_diff.1.gz /usr/share/man/man1/cg_merge.1.gz /usr/share/man/man1/ms_print.1.gz /usr/share/man/man1/valgrind-di-server.1.gz /usr/share/man/man1/valgrind-listener.1.gz /usr/share/man/man1/valgrind.1.gz /usr/share/man/man1/vgdb.1.gz /usr/share/valgrind /usr/share/valgrind/dh_view.css /usr/share/valgrind/dh_view.html /usr/share/valgrind/dh_view.js
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Jul 9 20:22:04 2024