Date: Wed, 18 Oct 2023 13:43:42 +0200 From: Paul Floyd <paulf2718@gmail.com> To: "freebsd-hackers@FreeBSD.org" <freebsd-hackers@FreeBSD.org> Subject: Valgrind 3.22 RC1 announced Message-ID: <01a7debc-bdc4-4aba-9f8d-1b78a00aac3c@gmail.com>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------FkSLwtkHSHIX51iMCOBIbiB1
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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-developers@lists.sourceforge.net
<mailto:valgrind-developers@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
--------------FkSLwtkHSHIX51iMCOBIbiB1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi</p>
<div
class="_3xX726aBn29LDbsDtzr_6E _1Ap4F5maDtT1E1YuCiaO0r D3IL3FD0RFy_mkKLPwL4"
style="max-width:800px" data-click-id="text"
data-adclicklocation="media">
<div class="_292iotee39Lmt0MkQZ2hPV RichTextJSON-root">
<p class="_1qeIAgB0cPwnLhDF9XSiJM">Below is the announcement for
Valgrind 3.22 RC1</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">I'd really appreciate it if
anyone can download build, and check it.</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">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!<br>
</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">The main thing that I've
worked on for this release is a major overhaul of aligned
allocation/deallocation and sized deallocation</p>
<ol class="_1eJr7K139jnMstd4HajqYP">
<li class="_3gqTEjt4x9UIIpWiro7YXz">
<p class="_1qeIAgB0cPwnLhDF9XSiJM">Previously the behaviour
was mostly "like GNU libc" no matter the platform. Now
Valgrind tries to behave like the build platform.</p>
</li>
<li class="_3gqTEjt4x9UIIpWiro7YXz">
<p class="_1qeIAgB0cPwnLhDF9XSiJM">Previously there was no
checking that alignment values were valid, now there is.</p>
</li>
<li class="_3gqTEjt4x9UIIpWiro7YXz">
<p class="_1qeIAgB0cPwnLhDF9XSiJM">Previously there was no
checking that deallocation alignment or size matchees the
allocation alignment and size, now there is.</p>
</li>
</ol>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">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.</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">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.</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM"><br>
</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">The mailing list referenced
in the announcement is</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM"><a
href="mailto:valgrind-developers@lists.sourceforge.net"
class="_3t5uN8xUmg0TOwRCOGQEcU moz-txt-link-freetext"
rel="noopener nofollow ugc" target="_blank">valgrind-developers@lists.sourceforge.net</a></p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">Announcement ===></p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">An RC1 tarball for 3.22.0 is
now available at<br>
<a
href="https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2"
class="_3t5uN8xUmg0TOwRCOGQEcU moz-txt-link-freetext"
rel="noopener nofollow ugc" target="_blank">https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2</a><br>;
(md5sum = 786715e301f9b1d3e10faf2a5b360598)<br>
(sha1sum = ea0e9ca5b5c45168bfcb795e1d19d9d3f5d58223)<br>
<a
href="https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2.asc"
class="_3t5uN8xUmg0TOwRCOGQEcU moz-txt-link-freetext"
rel="noopener nofollow ugc" target="_blank">https://sourceware.org/pub/valgrind/valgrind-3.22.0.RC1.tar.bz2.asc</a><br>;
Please give it a try in configurations that are important for
you and<br>
report any problems you have, either on this mailing list, or<br>
(preferably) via our bug tracker at<br>
<a href="https://bugs.kde.org/enter_bug.cgi?product=valgrind"
class="_3t5uN8xUmg0TOwRCOGQEcU moz-txt-link-freetext"
rel="noopener nofollow ugc" target="_blank">https://bugs.kde.org/enter_bug.cgi?product=valgrind</a><br>;
RC2 will appear in one week, Tuesday 24 October. And if
nothing<br>
critical emerges after that, a final release will happen a
week after<br>
that on Tuesday 31 October.</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM"><br>
</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM"><br>
</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">A+</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM">Paul</p>
<p class="_1qeIAgB0cPwnLhDF9XSiJM"><br>
</p>
</div>
</div>
<p></p>
</body>
</html>
--------------FkSLwtkHSHIX51iMCOBIbiB1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01a7debc-bdc4-4aba-9f8d-1b78a00aac3c>