- 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)
- add aarch64-support.diff, aarch64-VEX-support.diff: aarch64 support
- add armv6-support.diff: Add support for armv6hl
- Add Source URL, see https://en.opensuse.org/SourceUrls
- Fix last patch
- Add valgrind-glibc-2.17.patch to fix compilation with glibc 2.17
* The C++ demangler has been updated so as to work well with C++
* See https://bugs.kde.org/show_bug.cgi?id=290719
- fix build on ppc (32bit)
* 3.4.1 is a bug-fix release that fixes some regressions and
- fix divisions by zero in massif (#310234)
- update suppressions
- fix valgrind on x86_64 (#296803)
- suppression update
- update to 3.2.2:
recent binutils
* lots of emulation fixlets
- update to 3.1.1 (FATE #300493)
- various updates from branch to fix PPC32 support
- Fix GDB support
- update to 3.1 branch
- fix strict-aliasing issue
OBS-URL: https://build.opensuse.org/request/show/1119663
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/valgrind?expand=0&rev=145
* 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)
- add aarch64-support.diff, aarch64-VEX-support.diff: aarch64 support
- add armv6-support.diff: Add support for armv6hl
- Add Source URL, see https://en.opensuse.org/SourceUrls
- Fix last patch
- Add valgrind-glibc-2.17.patch to fix compilation with glibc 2.17
* The C++ demangler has been updated so as to work well with C++
* See https://bugs.kde.org/show_bug.cgi?id=290719
- fix build on ppc (32bit)
* 3.4.1 is a bug-fix release that fixes some regressions and
- fix divisions by zero in massif (#310234)
- update suppressions
- fix valgrind on x86_64 (#296803)
- suppression update
- update to 3.2.2:
recent binutils
* lots of emulation fixlets
- update to 3.1.1 (FATE #300493)
- various updates from branch to fix PPC32 support
- Fix GDB support
- update to 3.1 branch
- fix strict-aliasing issue
- 3.1.0 final update
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=266
- 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
OBS-URL: https://build.opensuse.org/request/show/1087804
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/valgrind?expand=0&rev=143
* 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
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=259
- 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.
OBS-URL: https://build.opensuse.org/request/show/1031320
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/valgrind?expand=0&rev=140
* 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.
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=253
- update to 3.17.0:
* 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
OBS-URL: https://build.opensuse.org/request/show/880364
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/valgrind?expand=0&rev=131
* 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
OBS-URL: https://build.opensuse.org/package/show/devel:tools/valgrind?expand=0&rev=235
- Use autopatch
- Change armv6-support.diff to a/b format
- 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.
OBS-URL: https://build.opensuse.org/request/show/816789
OBS-URL: https://build.opensuse.org/package/show/openSUSE:Factory/valgrind?expand=0&rev=126
