Paul Floyd
2023-10-18 11:43:42 UTC
Hi
Below is the announcement for Valgrind 3.22 RC1
I'd really appreciate it if anyone can download build, and check it.
Specific to FreeBSD, there ren't many new things compared to the current
devel/freebsd-devel port/package (on the other hand the devel/valgrind
devel is still on Valgrind 3.21 release plus a couple of patches). The
main thing is that if Valgrind itself crashes it should now print a
human readable callstack. Useful for bug reports!
The main thing that I've worked on for this release is a major overhaul
of aligned allocation/deallocation and sized deallocation
1.
Previously the behaviour was mostly "like GNU libc" no matter the
platform. Now Valgrind tries to behave like the build platform.
2.
Previously there was no checking that alignment values were valid,
now there is.
3.
Previously there was no checking that deallocation alignment or size
matchees the allocation alignment and size, now there is.
For the C++ allocation operators, unless you are writing a compiler or
allocator library it is unlikely that you will ever encounter these
issues since it's the compiler that translates new and delete
expressions into calls to operator new and operator delete.
Users of Cachegrind can now use annotation to start and stop
instrumentation. That allows you to focus on the code you want to
analyse and reduces the runtime burden.
The mailing list referenced in the announcement is
valgrind-***@lists.sourceforge.net
<mailto:valgrind-***@lists.sourceforge.net>
Announcement ===>
An RC1 tarball for 3.22.0 is now available at
https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2
<https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2>
(md5sum = 786715e301f9b1d3e10faf2a5b360598)
(sha1sum = ea0e9ca5b5c45168bfcb795e1d19d9d3f5d58223)
https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2.asc
<https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2.asc>
Please give it a try in configurations that are important for you and
report any problems you have, either on this mailing list, or
(preferably) via our bug tracker at
https://bugs.kde.org/enter_bug.cgi?product=valgrind
<https://bugs.kde.org/enter_bug.cgi?product=valgrind>
RC2 will appear in one week, Tuesday 24 October. And if nothing
critical emerges after that, a final release will happen a week after
that on Tuesday 31 October.
A+
Paul
Below is the announcement for Valgrind 3.22 RC1
I'd really appreciate it if anyone can download build, and check it.
Specific to FreeBSD, there ren't many new things compared to the current
devel/freebsd-devel port/package (on the other hand the devel/valgrind
devel is still on Valgrind 3.21 release plus a couple of patches). The
main thing is that if Valgrind itself crashes it should now print a
human readable callstack. Useful for bug reports!
The main thing that I've worked on for this release is a major overhaul
of aligned allocation/deallocation and sized deallocation
1.
Previously the behaviour was mostly "like GNU libc" no matter the
platform. Now Valgrind tries to behave like the build platform.
2.
Previously there was no checking that alignment values were valid,
now there is.
3.
Previously there was no checking that deallocation alignment or size
matchees the allocation alignment and size, now there is.
For the C++ allocation operators, unless you are writing a compiler or
allocator library it is unlikely that you will ever encounter these
issues since it's the compiler that translates new and delete
expressions into calls to operator new and operator delete.
Users of Cachegrind can now use annotation to start and stop
instrumentation. That allows you to focus on the code you want to
analyse and reduces the runtime burden.
The mailing list referenced in the announcement is
valgrind-***@lists.sourceforge.net
<mailto:valgrind-***@lists.sourceforge.net>
Announcement ===>
An RC1 tarball for 3.22.0 is now available at
https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2
<https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2>
(md5sum = 786715e301f9b1d3e10faf2a5b360598)
(sha1sum = ea0e9ca5b5c45168bfcb795e1d19d9d3f5d58223)
https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2.asc
<https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2.asc>
Please give it a try in configurations that are important for you and
report any problems you have, either on this mailing list, or
(preferably) via our bug tracker at
https://bugs.kde.org/enter_bug.cgi?product=valgrind
<https://bugs.kde.org/enter_bug.cgi?product=valgrind>
RC2 will appear in one week, Tuesday 24 October. And if nothing
critical emerges after that, a final release will happen a week after
that on Tuesday 31 October.
A+
Paul