You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
(1) |
2
|
3
(4) |
4
(3) |
5
(3) |
6
(3) |
|
7
|
8
(2) |
9
(3) |
10
(1) |
11
|
12
|
13
|
|
14
|
15
|
16
(3) |
17
|
18
(8) |
19
(2) |
20
(5) |
|
21
|
22
|
23
|
24
|
25
|
26
|
27
(2) |
|
28
(2) |
29
|
30
|
31
|
|
|
|
|
From: Julian S. <js...@ac...> - 2018-10-16 09:56:55
|
We are pleased to announce a new release of Valgrind, version 3.14.0, available from http://www.valgrind.org. 3.14.0 updates support for existing platforms. There are, as ever, many refinements and bug fixes. The release notes below give more details. Our thanks to all those who contribute to Valgrind's development. This release represents a great deal of time, energy and effort on the part of many people. Unfortunately the Solaris port no longer has a maintainer. If you have some familiarity with low level Solaris system programming and would like to help out, please get in touch. We are also looking for further assistance with the MacOS port. Happy and productive debugging and profiling, -- The Valgrind Developers Release 3.14.0 (9 October 2018) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.14.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, AMD64/macOS 10.13. * ==================== CORE CHANGES =================== * 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. * ================== PLATFORM CHANGES ================= * 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. * ==================== TOOL CHANGES ==================== * 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]. * ==================== OTHER CHANGES ==================== * 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. * ==================== FIXED BUGS ==================== The following bugs have been fixed or resolved. Note that "n-i-bz" stands for "not in bugzilla" -- that is, a bug that was reported to us but never got a bugzilla entry. We encourage you to file bugs in bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather than mailing the developers (or mailing lists) directly -- bugs that are not entered into bugzilla tend to get forgotten about or ignored. To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX where XXXXXX is the bug number as listed below. 79362 Debug info is lost for .so files when they are dlclose'd 208052 strlcpy error when n = 0 255603 exp-sgcheck Assertion '!already_present' failed 338252 building valgrind with -flto (link time optimisation) fails 345763 MIPS N32 ABI support 368913 WARNING: unhandled arm64-linux syscall: 117 (ptrace) == 388664 unhandled arm64-linux syscall: 117 (ptrace) 372347 Replacement problem of the additional c++14/c++17 new/delete operators 373069 memcheck/tests/leak_cpp_interior fails with GCC 5.1+ 376257 helgrind history full speed up using a cached stack 379373 Fix syscall param msg->desc.port.name points to uninitialised byte(s) on macOS 10.12 379748 Fix missing pselect syscall (OS X 10.11) 379754 Fix missing syscall ulock_wait (OS X 10.12) 380397 s390x: __GI_strcspn() replacemenet needed 381162 possible array overrun in VEX register allocator 381272 ppc64 doesn't compile test_isa_2_06_partx.c without VSX support 381274 powerpc too chatty even with --sigill-diagnostics=no 381289 epoll_pwait can have a NULL sigmask 381553 VEX register allocator v3 381556 arm64: Handle feature registers access on 4.11 Linux kernel or later 381769 Use ucontext_t instead of struct ucontext 381805 arm32 needs ld.so index hardwire for new glibc security fixes 382256 gz compiler flag test doesn't work for gold 382407 vg_perf needs "--terse" command line option 382515 "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/[..] 382563 MIPS MSA ASE support 382998 xml-socket doesn't work 383275 massif: m_xarray.c:162 (ensureSpaceXA): Assertion '!xa->arr' failed 383723 Fix missing kevent_qos syscall (macOS 10.11) == 385604 illegal hardware instruction (OpenCV cv::namedWindow) 384096 Mention AddrCheck at Memcheck's command line option [..] 384230 vex x86->IR: 0x67 0xE8 0xAB 0x68 == 384156 vex x86->IR: 0x67 0xE8 0x6B 0x6A == 386115 vex x86->IR: 0x67 0xE8 0xD3 0x8B any program == 388407 vex x86->IR: 0x67 0xE8 0xAB 0x29 == 394903 vex x86->IR: 0x67 0xE8 0x1B 0xDA 384337 performance improvements to VEX register allocator v2 and v3 384526 reduce number of spill insns generated by VEX register allocator v3 384584 Callee saved regs listed first for AMD64, X86, and PPC architectures 384631 Sanitise client args as printed with -v 384633 Add a simple progress-reporting facility 384987 VEX regalloc: allocate caller-save registers for short lived vregs 385055 PPC VEX temporary storage exhausted 385182 PPC64 is missing support for the DSCR 385183 PPC64, Add support for xscmpeqdp, xscmpgtdp, xscmpgedp, xsmincdp 385207 PPC64, generate_store_FPRF() generates too many Iops 385208 PPC64, xxperm instruction exhausts temporary memory 385210 PPC64, vpermr instruction could exhaust temporary memory 385279 unhandled syscall: mach:43 (mach_generate_activity_id) == 395136 valgrind: m_syswrap/syswrap-main.c:438 (Bool eq_Syscall[..] == 387045 Valgrind crashing on High Sierra when testing any newly [..] 385334 PPC64, fix vpermr, xxperm, xxpermr mask value. 385408 s390x: z13 vector "support" instructions not implemented 385409 s390x: z13 vector integer instructions not implemented 385410 s390x: z13 vector string instructions not implemented 385412 s390x: new non-vector z13 instructions not implemented 385868 glibc ld.so _dl_runtime_resolve_avx_slow conditional jump warning. 385912 none/tests/rlimit_nofile fails on newer glibc/kernel. 385939 Optionally exit on the first error 386318 valgrind.org/info/tools.html is missing SGCheck 386425 running valgrind + wine on armv7l gives illegal opcode 386397 PPC64, valgrind truncates powerpc timebase to 32-bits. 387410 MIPSr6 support 387664 Memcheck: make expensive-definedness-checks be the default 387712 s390x cgijnl reports Conditional jump depends on uninitialised value 387766 asm shifts cause false positive "Conditional jump or move depends on uninitialised value" 387773 .gnu_debugaltlink paths resolve relative to .debug file, not symlink 388174 valgrind with Wine quits with "Assertion 'cfsi_fits' failed" 388786 Support bpf syscall in amd64 Linux 388862 Add replacements for wmemchr and wcsnlen on Linux 389065 valgrind meets gcc flag -Wlogical-op 389373 exp-sgcheck the 'impossible' happened as Ist_LoadG is not instrumented 390471 suppression by specification of source-file line number 390723 make xtree dump files world wide readable, similar to log files 391164 constraint bug in tests/ppc64/test_isa_2_07_part1.c for mtfprwa 391861 Massif Assertion 'n_ips >= 1 && n_ips <= VG_(clo_backtrace_size)' 392118 unhandled amd64-linux syscall: 332 (statx) 392449 callgrind not clearing the number of calls properly 393017 Add missing support for xsmaxcdp instruction, bug fixes for xsmincdp, lxssp, stxssp and stxvl instructions. 393023 callgrind_control risks using the wrong vgdb 393062 build-id ELF phdrs read causes "debuginfo reader: ensure_valid failed" 393099 posix_memalign() invalid write if alignment == 0 393146 failing assert "is_DebugInfo_active(di)" 395709 PPC64 is missing support for the xvnegsp instruction 395682 Accept read-only PT_LOAD segments and .rodata by ld -z separate-code == 384727 396475 valgrind OS-X build: config.h not found (out-of-tree macOS builds) 395991 arm-linux: wine's unit tests enter a signal delivery loop [..] 396839 s390x: Trap instructions not implemented 396887 arch_prctl should return EINVAL on unknown option == 397286 crash before launching binary (Unsupported arch_prctl option) == 397393 valgrind: the 'impossible' happened: (Archlinux) == 397521 valgrind: the 'impossible' happened: Unsupported [..] 396906 compile tests failure on mips32-linux: broken inline asm in tests on mips32-linux 397012 glibc ld.so uses arch_prctl on i386 397089 amd64: Incorrect decoding of three-register vmovss/vmovsd opcode 11h 397354 utimensat should ignore timespec tv_sec if tv_nsec is UTIME_NOW/OMIT 397424 glibc 2.27 and gdb_server tests 398028 Assertion `cfsi_fits` failing in simple C program 398066 s390x: cgijl dep1, 0 reports false unitialised values warning n-i-bz Fix missing workq_ops operations (macOS) n-i-bz fix bug in strspn replacement n-i-bz Add support for the Linux BLKFLSBUF ioctl n-i-bz Add support for the Linux BLKREPORTZONE and BLKRESETZONE ioctls n-i-bz Fix possible stack trashing by semctl syscall wrapping n-i-bz Add support for the Linux membarrier() system call n-i-bz x86 front end: recognise and handle UD2 correctly n-i-bz Signal delivery for x86-linux: ensure that the stack pointer is correctly aligned before entering the handler. (3.14.0.RC1: 30 September 2018, git c2aeea2d28acb0639bcc8cc1e4ab115067db1eae) (3.14.0.RC2: 3 October 2018, git 3e214c4858a6fdd5697e767543a0c19e30505582) (3.14.0: 9 October 2018, git 353a3587bb0e2757411f9138f5e936728ed6cc4f) |
|
From: <sv...@va...> - 2018-10-16 09:45:05
|
Author: sewardj
Date: Tue Oct 16 10:20:06 2018
New Revision: 532
Log:
Update for 3.14.0.
Modified:
trunk/downloads/current.html
trunk/php/.htconfx
Modified: trunk/downloads/current.html
==============================================================================
--- trunk/downloads/current.html (original)
+++ trunk/downloads/current.html Tue Oct 16 10:20:06 2018
@@ -17,6 +17,22 @@
<div id="release">
+<a name="current"><h3>Valgrind 3.14.0</h3></a>
+
+<p><a href="http://www.valgrind.org/downloads/valgrind-3.14.0.tar.bz2">valgrind 3.14.0
+ (tar.bz2)</a> [17MB] - 9 October 2018.<br /> For
+ {x86,amd64,arm32,arm64,ppc32,ppc64le,ppc64be,s390x,mips32,mips64}-linux,
+ {arm32,arm64,x86,mips32}-android, {x86,amd64}-solaris and
+ {x86,amd64}-darwin (Mac OS X 10.13).<br />
+<span class="md5sum">md5: 74175426afa280184b62591b58c671b3</span></p>
+
+<p> 3.14.0 updates support for existing platforms. There are, as ever, many
+ smaller refinements and bug fixes. See the
+ <a href="/docs/manual/dist.news.html">release notes</a> for details.
+</p>
+
+
+<!--
<a name="current"><h3>Valgrind 3.13.0</h3></a>
<p><a href="ftp://sourceware.org/pub/valgrind/valgrind-3.13.0.tar.bz2">valgrind 3.13.0
@@ -32,7 +48,7 @@
bug fixes. See the
<a href="/docs/manual/dist.news.html">release notes</a> for details.
</p>
-
+-->
<!--
<div id="release">
Modified: trunk/php/.htconfx
==============================================================================
--- trunk/php/.htconfx (original)
+++ trunk/php/.htconfx Tue Oct 16 10:20:06 2018
@@ -24,11 +24,11 @@
'inc_dir' => $base_dir . '/php/',
'img_dir' => $base_dir . '/images/',
- 'dt_copyright' => '2000-2017',
+ 'dt_copyright' => '2000-2018',
/* current release info */
- 'release-date' => '14 June 2017',
- 'release-version' => 'valgrind-3.13.0',
+ 'release-date' => '9 October 2018',
+ 'release-version' => 'valgrind-3.14.0',
/* mailing lists, bug reports, etc. */
'vgannounce' => array(
|
|
From: <sv...@va...> - 2018-10-16 09:40:10
|
Author: sewardj
Date: Tue Oct 16 10:31:06 2018
New Revision: 533
Log:
Update docs for 3.14.0.
Modified:
trunk/docs/manual/FAQ.html
trunk/docs/manual/QuickStart.html
trunk/docs/manual/bbv-manual.html
trunk/docs/manual/cg-manual.html
trunk/docs/manual/cl-format.html
trunk/docs/manual/cl-manual.html
trunk/docs/manual/design-impl.html
trunk/docs/manual/dh-manual.html
trunk/docs/manual/dist.authors.html
trunk/docs/manual/dist.html
trunk/docs/manual/dist.news.html
trunk/docs/manual/dist.news.old.html
trunk/docs/manual/dist.readme-android.html
trunk/docs/manual/dist.readme-developers.html
trunk/docs/manual/dist.readme-missing.html
trunk/docs/manual/dist.readme-packagers.html
trunk/docs/manual/dist.readme-s390.html
trunk/docs/manual/dist.readme.html
trunk/docs/manual/drd-manual.html
trunk/docs/manual/faq.html
trunk/docs/manual/hg-manual.html
trunk/docs/manual/index.html
trunk/docs/manual/license.gfdl.html
trunk/docs/manual/license.gpl.html
trunk/docs/manual/licenses.html
trunk/docs/manual/lk-manual.html
trunk/docs/manual/manual-core-adv.html
trunk/docs/manual/manual-core.html
trunk/docs/manual/manual-intro.html
trunk/docs/manual/manual-writing-tools.html
trunk/docs/manual/manual.html
trunk/docs/manual/mc-manual.html
trunk/docs/manual/ms-manual.html
trunk/docs/manual/nl-manual.html
trunk/docs/manual/quick-start.html
trunk/docs/manual/sg-manual.html
trunk/docs/manual/tech-docs.html
trunk/docs/manual/valgrind_manual.html.tar.bz2
trunk/docs/manual/valgrind_manual.pdf
trunk/docs/manual/valgrind_manual.ps.bz2
Modified: trunk/docs/manual/FAQ.html
==============================================================================
--- trunk/docs/manual/FAQ.html (original)
+++ trunk/docs/manual/FAQ.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Valgrind FAQ</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="index.html" title="Valgrind Documentation">
<link rel="prev" href="nl-manual.html" title="14. Nulgrind: the minimal Valgrind tool">
@@ -22,10 +22,10 @@
<div>
<div><h1 class="title">
<a name="FAQ"></a>Valgrind FAQ</h1></div>
-<div><p class="releaseinfo">Release 3.13.0 15 June 2017</p></div>
-<div><p class="copyright">Copyright © 2000-2017 <a class="ulink" href="http://www.valgrind.org/info/developers.html" target="_top">Valgrind Developers</a></p></div>
+<div><p class="releaseinfo">Release 3.14.0 9 October 2018</p></div>
+<div><p class="copyright">Copyright © 2000-2018 <a class="ulink" href="http://www.valgrind.org/info/developers.html" target="_top">Valgrind Developers</a></p></div>
<div><div class="legalnotice">
-<a name="idm140394923825504"></a><p>Email: <a class="ulink" href="mailto:val...@va..." target="_top">val...@va...</a></p>
+<a name="idm139771388424960"></a><p>Email: <a class="ulink" href="mailto:val...@va..." target="_top">val...@va...</a></p>
</div></div>
</div>
<hr>
Modified: trunk/docs/manual/QuickStart.html
==============================================================================
--- trunk/docs/manual/QuickStart.html (original)
+++ trunk/docs/manual/QuickStart.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>The Valgrind Quick Start Guide</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="index.html" title="Valgrind Documentation">
<link rel="prev" href="index.html" title="Valgrind Documentation">
@@ -22,10 +22,10 @@
<div>
<div><h1 class="title">
<a name="QuickStart"></a>The Valgrind Quick Start Guide</h1></div>
-<div><p class="releaseinfo">Release 3.13.0 15 June 2017</p></div>
-<div><p class="copyright">Copyright © 2000-2017 <a class="ulink" href="http://www.valgrind.org/info/developers.html" target="_top">Valgrind Developers</a></p></div>
+<div><p class="releaseinfo">Release 3.14.0 9 October 2018</p></div>
+<div><p class="copyright">Copyright © 2000-2018 <a class="ulink" href="http://www.valgrind.org/info/developers.html" target="_top">Valgrind Developers</a></p></div>
<div><div class="legalnotice">
-<a name="idm140394929811680"></a><p>Email: <a class="ulink" href="mailto:val...@va..." target="_top">val...@va...</a></p>
+<a name="idm139771388209664"></a><p>Email: <a class="ulink" href="mailto:val...@va..." target="_top">val...@va...</a></p>
</div></div>
</div>
<hr>
Modified: trunk/docs/manual/bbv-manual.html
==============================================================================
--- trunk/docs/manual/bbv-manual.html (original)
+++ trunk/docs/manual/bbv-manual.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>12. BBV: an experimental basic block vector generation tool</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="sg-manual.html" title="11. SGCheck: an experimental stack and global array overrun detector">
Modified: trunk/docs/manual/cg-manual.html
==============================================================================
--- trunk/docs/manual/cg-manual.html (original)
+++ trunk/docs/manual/cg-manual.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>5. Cachegrind: a cache and branch-prediction profiler</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="mc-manual.html" title="4. Memcheck: a memory error detector">
@@ -886,7 +886,7 @@
<pre class="programlisting">
enum E { A, B, C };
enum E e;
-enum E table[] = { 1, 2, 3 };
+int table[] = { 1, 2, 3 };
int i;
...
i += table[e];
Modified: trunk/docs/manual/cl-format.html
==============================================================================
--- trunk/docs/manual/cl-format.html (original)
+++ trunk/docs/manual/cl-format.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>3. Callgrind Format Specification</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="tech-docs.html" title="Valgrind Technical Documentation">
<link rel="prev" href="manual-writing-tools.html" title="2. Writing a New Valgrind Tool">
Modified: trunk/docs/manual/cl-manual.html
==============================================================================
--- trunk/docs/manual/cl-manual.html (original)
+++ trunk/docs/manual/cl-manual.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>6. Callgrind: a call-graph generating cache and branch prediction profiler</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="cg-manual.html" title="5. Cachegrind: a cache and branch-prediction profiler">
@@ -75,7 +75,7 @@
<p>This command reads in the profile data, and prints a
sorted lists of functions, optionally with source annotation.</p>
<p>For graphical visualization of the data, try
- <a class="ulink" href="http://kcachegrind.sourceforge.net/cgi-bin/show.cgi/KcacheGrindIndex" target="_top">KCachegrind</a>, which is a KDE/Qt based
+ <a class="ulink" href="https://kcachegrind.github.io/html/Home.html" target="_top">KCachegrind</a>, which is a KDE/Qt based
GUI that makes it easy to navigate the large amount of data that
Callgrind produces.</p>
</dd>
@@ -187,7 +187,7 @@
<code class="computeroutput">cg_annotate</code>.
</p>
<p>For better call graph browsing experience, it is highly recommended
- to use <a class="ulink" href="http://kcachegrind.sourceforge.net/cgi-bin/show.cgi/KcacheGrindIndex" target="_top">KCachegrind</a>.
+ to use <a class="ulink" href="https://kcachegrind.github.io/html/Home.html" target="_top">KCachegrind</a>.
If your code
has a significant fraction of its cost in <span class="emphasis"><em>cycles</em></span> (sets
of functions calling each other in a recursive manner), you have to
@@ -268,7 +268,7 @@
must be actively running for detection of the dump command. So,
for a GUI application, resize the window, or for a server, send a
request.</p>
-<p>If you are using <a class="ulink" href="http://kcachegrind.sourceforge.net/cgi-bin/show.cgi/KcacheGrindIndex" target="_top">KCachegrind</a>
+<p>If you are using <a class="ulink" href="https://kcachegrind.github.io/html/Home.html" target="_top">KCachegrind</a>
for browsing of profile information, you can use the toolbar
button <span class="command"><strong>Force dump</strong></span>. This will request a dump
and trigger a reload after the dump is written.</p>
Modified: trunk/docs/manual/design-impl.html
==============================================================================
--- trunk/docs/manual/design-impl.html (original)
+++ trunk/docs/manual/design-impl.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>1. The Design and Implementation of Valgrind</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="tech-docs.html" title="Valgrind Technical Documentation">
<link rel="prev" href="tech-docs.html" title="Valgrind Technical Documentation">
Modified: trunk/docs/manual/dh-manual.html
==============================================================================
--- trunk/docs/manual/dh-manual.html (original)
+++ trunk/docs/manual/dh-manual.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>10. DHAT: a dynamic heap analysis tool</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="ms-manual.html" title="9. Massif: a heap profiler">
@@ -26,9 +26,9 @@
<dt><span class="sect1"><a href="dh-manual.html#dh-manual.overview">10.1. Overview</a></span></dt>
<dt><span class="sect1"><a href="dh-manual.html#dh-manual.understanding">10.2. Understanding DHAT's output</a></span></dt>
<dd><dl>
-<dt><span class="sect2"><a href="dh-manual.html#idm140394924138288">10.2.1. Interpreting the max-live, tot-alloc and deaths fields</a></span></dt>
-<dt><span class="sect2"><a href="dh-manual.html#idm140394926128304">10.2.2. Interpreting the acc-ratios fields</a></span></dt>
-<dt><span class="sect2"><a href="dh-manual.html#idm140394925890256">10.2.3. Interpreting "Aggregated access counts by offset" data</a></span></dt>
+<dt><span class="sect2"><a href="dh-manual.html#idm139771384591744">10.2.1. Interpreting the max-live, tot-alloc and deaths fields</a></span></dt>
+<dt><span class="sect2"><a href="dh-manual.html#idm139771384048256">10.2.2. Interpreting the acc-ratios fields</a></span></dt>
+<dt><span class="sect2"><a href="dh-manual.html#idm139771379392032">10.2.3. Interpreting "Aggregated access counts by offset" data</a></span></dt>
</dl></dd>
<dt><span class="sect1"><a href="dh-manual.html#dh-manual.options">10.3. DHAT Command-line Options</a></span></dt>
</dl>
@@ -90,9 +90,9 @@
numbers. That is best illustrated via a set of examples.</p>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
-<a name="idm140394924138288"></a>10.2.1. Interpreting the max-live, tot-alloc and deaths fields</h3></div></div></div>
+<a name="idm139771384591744"></a>10.2.1. Interpreting the max-live, tot-alloc and deaths fields</h3></div></div></div>
<div class="sect3"><div class="titlepage"><div><div><h4 class="title">
-<a name="idm140394924137584"></a>10.2.1.1. A simple example</h4></div></div></div></div>
+<a name="idm139771384591040"></a>10.2.1.1. A simple example</h4></div></div></div></div>
<pre class="screen">
======== SUMMARY STATISTICS ========
@@ -123,7 +123,7 @@
for 1,045,339,534 instructions, and so the average age at death is
about 2% of the program's total run time.</p>
<div class="sect3"><div class="titlepage"><div><div><h4 class="title">
-<a name="idm140394923815680"></a>10.2.1.2. Example of a potential process-lifetime leak</h4></div></div></div></div>
+<a name="idm139771383650416"></a>10.2.1.2. Example of a potential process-lifetime leak</h4></div></div></div></div>
<p>This next example (from a different program than the above)
shows a potential process lifetime leak. A process lifetime leak
occurs when a program keeps allocating data, but only frees the
@@ -158,9 +158,9 @@
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
-<a name="idm140394926128304"></a>10.2.2. Interpreting the acc-ratios fields</h3></div></div></div>
+<a name="idm139771384048256"></a>10.2.2. Interpreting the acc-ratios fields</h3></div></div></div>
<div class="sect3"><div class="titlepage"><div><div><h4 class="title">
-<a name="idm140394923814880"></a>10.2.2.1. A fairly harmless allocation point record</h4></div></div></div></div>
+<a name="idm139771384047504"></a>10.2.2.1. A fairly harmless allocation point record</h4></div></div></div></div>
<pre class="screen">
max-live: 49,398 in 808 blocks
tot-alloc: 1,481,940 in 24,240 blocks (avg size 61.13)
@@ -193,7 +193,7 @@
that they must have varying sizes since the average block size, 61.13,
isn't a whole number.</p>
<div class="sect3"><div class="titlepage"><div><div><h4 class="title">
-<a name="idm140394922011696"></a>10.2.2.2. A more suspicious looking example</h4></div></div></div></div>
+<a name="idm139771394771296"></a>10.2.2.2. A more suspicious looking example</h4></div></div></div></div>
<pre class="screen">
max-live: 180,224 in 22 blocks
tot-alloc: 180,224 in 22 blocks (avg size 8192.00)
@@ -213,7 +213,7 @@
DHAT can tell us, that Memcheck can't, is that not only are the blocks
leaked, they are also never used.</p>
<div class="sect3"><div class="titlepage"><div><div><h4 class="title">
-<a name="idm140394922008704"></a>10.2.2.3. Another suspicious example</h4></div></div></div></div>
+<a name="idm139771394768272"></a>10.2.2.3. Another suspicious example</h4></div></div></div></div>
<p>Here's one where blocks are allocated, written to,
but never read from. We see this immediately from the zero read
access ratio. They do get freed, though:</p>
@@ -241,7 +241,7 @@
</div>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
-<a name="idm140394925890256"></a>10.2.3. Interpreting "Aggregated access counts by offset" data</h3></div></div></div>
+<a name="idm139771379392032"></a>10.2.3. Interpreting "Aggregated access counts by offset" data</h3></div></div></div>
<p>For allocation points that always allocate blocks of the same
size, and which are 4096 bytes or smaller, DHAT counts accesses
per offset, for example:</p>
Modified: trunk/docs/manual/dist.authors.html
==============================================================================
--- trunk/docs/manual/dist.authors.html (original)
+++ trunk/docs/manual/dist.authors.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>1. AUTHORS</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.html" title="Valgrind Distribution Documents">
@@ -105,6 +105,8 @@
Maran Pakkirisamy implemented support for decimal floating point on<br>
s390.<br>
<br>
+Rhys Kidd updated and maintains the macOS port.<br>
+<br>
Many, many people sent bug reports, patches, and helpful feedback.<br>
<br>
Development of Valgrind was supported in part by the Tri-Lab Partners<br>
Modified: trunk/docs/manual/dist.html
==============================================================================
--- trunk/docs/manual/dist.html (original)
+++ trunk/docs/manual/dist.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Valgrind Distribution Documents</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="index.html" title="Valgrind Documentation">
<link rel="prev" href="cl-format.html" title="3. Callgrind Format Specification">
@@ -22,10 +22,10 @@
<div>
<div><h1 class="title">
<a name="dist"></a>Valgrind Distribution Documents</h1></div>
-<div><p class="releaseinfo">Release 3.13.0 15 June 2017</p></div>
-<div><p class="copyright">Copyright © 2000-2017 <a class="ulink" href="http://www.valgrind.org/info/developers.html" target="_top">Valgrind Developers</a></p></div>
+<div><p class="releaseinfo">Release 3.14.0 9 October 2018</p></div>
+<div><p class="copyright">Copyright © 2000-2018 <a class="ulink" href="http://www.valgrind.org/info/developers.html" target="_top">Valgrind Developers</a></p></div>
<div><div class="legalnotice">
-<a name="idm140394926016768"></a><p>Email: <a class="ulink" href="mailto:val...@va..." target="_top">val...@va...</a></p>
+<a name="idm139771385978320"></a><p>Email: <a class="ulink" href="mailto:val...@va..." target="_top">val...@va...</a></p>
</div></div>
</div>
<hr>
Modified: trunk/docs/manual/dist.news.html
==============================================================================
--- trunk/docs/manual/dist.news.html (original)
+++ trunk/docs/manual/dist.news.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>2. NEWS</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.authors.html" title="1. AUTHORS">
@@ -21,7 +21,200 @@
<div class="titlepage"><div><div><h1 class="title">
<a name="dist.news"></a>2. NEWS</h1></div></div></div>
<div class="literallayout"><p><br>
- Release 3.13.0 (15 June 2017)<br>
+ Release 3.14.0 (9 October 2018)<br>
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
+<br>
+3.14.0 is a feature release with many improvements and the usual collection of<br>
+bug fixes.<br>
+<br>
+This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux,<br>
+PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux,<br>
+MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android,<br>
+X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12. There is also preliminary<br>
+support for X86/macOS 10.13, AMD64/macOS 10.13.<br>
+<br>
+* ==================== CORE CHANGES ===================<br>
+<br>
+* The new option --keep-debuginfo=no|yes (default no) can be used to retain<br>
+ debug info for unloaded code. This allows saved stack traces (e.g. for<br>
+ memory leaks) to include file/line info for code that has been dlclose'd (or<br>
+ similar). See the user manual for more information and known limitations.<br>
+<br>
+* Ability to specify suppressions based on source file name and line number.<br>
+<br>
+* Majorly overhauled register allocator. No end-user changes, but the JIT<br>
+ generates code a bit more quickly now.<br>
+<br>
+* ================== PLATFORM CHANGES =================<br>
+<br>
+* Preliminary support for macOS 10.13 has been added.<br>
+<br>
+* mips: support for MIPS32/MIPS64 Revision 6 has been added.<br>
+<br>
+* mips: support for MIPS SIMD architecture (MSA) has been added.<br>
+<br>
+* mips: support for MIPS N32 ABI has been added.<br>
+<br>
+* s390: partial support for vector instructions (integer and string) has been<br>
+ added.<br>
+<br>
+* ==================== TOOL CHANGES ====================<br>
+<br>
+* Helgrind: Addition of a flag<br>
+ --delta-stacktrace=no|yes [yes on linux amd64/x86]<br>
+ which specifies how full history stack traces should be computed.<br>
+ Setting this to =yes can speed up Helgrind by 25% when using<br>
+ --history-level=full.<br>
+<br>
+* Memcheck: reduced false positive rate for optimised code created by Clang 6<br>
+ / LLVM 6 on x86, amd64 and arm64. In particular, Memcheck analyses code<br>
+ blocks more carefully to determine where it can avoid expensive definedness<br>
+ checks without loss of precision. This is controlled by the flag<br>
+ --expensive-definedness-checks=no|auto|yes [auto].<br>
+<br>
+* ==================== OTHER CHANGES ====================<br>
+<br>
+* Valgrind is now buildable with link-time optimisation (LTO). A new<br>
+ configure option --enable-lto=yes allows building Valgrind with LTO. If the<br>
+ toolchain supports it, this produces a smaller/faster Valgrind (up to 10%).<br>
+ Note that if you are doing Valgrind development, --enable-lto=yes massively<br>
+ slows down the build process.<br>
+<br>
+* ==================== FIXED BUGS ====================<br>
+<br>
+The following bugs have been fixed or resolved. Note that "n-i-bz"<br>
+stands for "not in bugzilla" -- that is, a bug that was reported to us<br>
+but never got a bugzilla entry. We encourage you to file bugs in<br>
+bugzilla (https://bugs.kde.org/enter_bug.cgi?product=valgrind) rather<br>
+than mailing the developers (or mailing lists) directly -- bugs that<br>
+are not entered into bugzilla tend to get forgotten about or ignored.<br>
+<br>
+To see details of a given bug, visit<br>
+ https://bugs.kde.org/show_bug.cgi?id=XXXXXX<br>
+where XXXXXX is the bug number as listed below.<br>
+<br>
+79362 Debug info is lost for .so files when they are dlclose'd<br>
+208052 strlcpy error when n = 0<br>
+255603 exp-sgcheck Assertion '!already_present' failed<br>
+338252 building valgrind with -flto (link time optimisation) fails<br>
+345763 MIPS N32 ABI support<br>
+368913 WARNING: unhandled arm64-linux syscall: 117 (ptrace)<br>
+ == 388664 unhandled arm64-linux syscall: 117 (ptrace)<br>
+372347 Replacement problem of the additional c++14/c++17 new/delete operators<br>
+373069 memcheck/tests/leak_cpp_interior fails with GCC 5.1+<br>
+376257 helgrind history full speed up using a cached stack<br>
+379373 Fix syscall param msg->desc.port.name points to uninitialised byte(s)<br>
+ on macOS 10.12<br>
+379748 Fix missing pselect syscall (OS X 10.11)<br>
+379754 Fix missing syscall ulock_wait (OS X 10.12)<br>
+380397 s390x: __GI_strcspn() replacemenet needed<br>
+381162 possible array overrun in VEX register allocator<br>
+381272 ppc64 doesn't compile test_isa_2_06_partx.c without VSX support<br>
+381274 powerpc too chatty even with --sigill-diagnostics=no<br>
+381289 epoll_pwait can have a NULL sigmask<br>
+381553 VEX register allocator v3<br>
+381556 arm64: Handle feature registers access on 4.11 Linux kernel or later<br>
+381769 Use ucontext_t instead of struct ucontext<br>
+381805 arm32 needs ld.so index hardwire for new glibc security fixes<br>
+382256 gz compiler flag test doesn't work for gold<br>
+382407 vg_perf needs "--terse" command line option<br>
+382515 "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/[..]<br>
+382563 MIPS MSA ASE support<br>
+382998 xml-socket doesn't work<br>
+383275 massif: m_xarray.c:162 (ensureSpaceXA): Assertion '!xa->arr' failed<br>
+383723 Fix missing kevent_qos syscall (macOS 10.11)<br>
+ == 385604 illegal hardware instruction (OpenCV cv::namedWindow)<br>
+384096 Mention AddrCheck at Memcheck's command line option [..]<br>
+384230 vex x86->IR: 0x67 0xE8 0xAB 0x68<br>
+ == 384156 vex x86->IR: 0x67 0xE8 0x6B 0x6A<br>
+ == 386115 vex x86->IR: 0x67 0xE8 0xD3 0x8B any program<br>
+ == 388407 vex x86->IR: 0x67 0xE8 0xAB 0x29<br>
+ == 394903 vex x86->IR: 0x67 0xE8 0x1B 0xDA<br>
+384337 performance improvements to VEX register allocator v2 and v3<br>
+384526 reduce number of spill insns generated by VEX register allocator v3<br>
+384584 Callee saved regs listed first for AMD64, X86, and PPC architectures<br>
+384631 Sanitise client args as printed with -v<br>
+384633 Add a simple progress-reporting facility<br>
+384987 VEX regalloc: allocate caller-save registers for short lived vregs<br>
+385055 PPC VEX temporary storage exhausted<br>
+385182 PPC64 is missing support for the DSCR<br>
+385183 PPC64, Add support for xscmpeqdp, xscmpgtdp, xscmpgedp, xsmincdp<br>
+385207 PPC64, generate_store_FPRF() generates too many Iops<br>
+385208 PPC64, xxperm instruction exhausts temporary memory<br>
+385210 PPC64, vpermr instruction could exhaust temporary memory<br>
+385279 unhandled syscall: mach:43 (mach_generate_activity_id)<br>
+ == 395136 valgrind: m_syswrap/syswrap-main.c:438 (Bool eq_Syscall[..]<br>
+ == 387045 Valgrind crashing on High Sierra when testing any newly [..]<br>
+385334 PPC64, fix vpermr, xxperm, xxpermr mask value.<br>
+385408 s390x: z13 vector "support" instructions not implemented<br>
+385409 s390x: z13 vector integer instructions not implemented<br>
+385410 s390x: z13 vector string instructions not implemented<br>
+385412 s390x: new non-vector z13 instructions not implemented<br>
+385868 glibc ld.so _dl_runtime_resolve_avx_slow conditional jump warning.<br>
+385912 none/tests/rlimit_nofile fails on newer glibc/kernel.<br>
+385939 Optionally exit on the first error<br>
+386318 valgrind.org/info/tools.html is missing SGCheck<br>
+386425 running valgrind + wine on armv7l gives illegal opcode<br>
+386397 PPC64, valgrind truncates powerpc timebase to 32-bits.<br>
+387410 MIPSr6 support<br>
+387664 Memcheck: make expensive-definedness-checks be the default<br>
+387712 s390x cgijnl reports Conditional jump depends on uninitialised value<br>
+387766 asm shifts cause false positive "Conditional jump or move depends<br>
+ on uninitialised value"<br>
+387773 .gnu_debugaltlink paths resolve relative to .debug file, not symlink<br>
+388174 valgrind with Wine quits with "Assertion 'cfsi_fits' failed"<br>
+388786 Support bpf syscall in amd64 Linux<br>
+388862 Add replacements for wmemchr and wcsnlen on Linux<br>
+389065 valgrind meets gcc flag -Wlogical-op<br>
+389373 exp-sgcheck the 'impossible' happened as Ist_LoadG is not instrumented<br>
+390471 suppression by specification of source-file line number<br>
+390723 make xtree dump files world wide readable, similar to log files<br>
+391164 constraint bug in tests/ppc64/test_isa_2_07_part1.c for mtfprwa<br>
+391861 Massif Assertion 'n_ips >= 1 && n_ips <= VG_(clo_backtrace_size)'<br>
+392118 unhandled amd64-linux syscall: 332 (statx)<br>
+392449 callgrind not clearing the number of calls properly<br>
+393017 Add missing support for xsmaxcdp instruction, bug fixes for xsmincdp,<br>
+ lxssp, stxssp and stxvl instructions.<br>
+393023 callgrind_control risks using the wrong vgdb<br>
+393062 build-id ELF phdrs read causes "debuginfo reader: ensure_valid failed"<br>
+393099 posix_memalign() invalid write if alignment == 0<br>
+393146 failing assert "is_DebugInfo_active(di)"<br>
+395709 PPC64 is missing support for the xvnegsp instruction<br>
+395682 Accept read-only PT_LOAD segments and .rodata by ld -z separate-code<br>
+ == 384727<br>
+396475 valgrind OS-X build: config.h not found (out-of-tree macOS builds)<br>
+395991 arm-linux: wine's unit tests enter a signal delivery loop [..]<br>
+396839 s390x: Trap instructions not implemented<br>
+396887 arch_prctl should return EINVAL on unknown option<br>
+ == 397286 crash before launching binary (Unsupported arch_prctl option)<br>
+ == 397393 valgrind: the 'impossible' happened: (Archlinux)<br>
+ == 397521 valgrind: the 'impossible' happened: Unsupported [..]<br>
+396906 compile tests failure on mips32-linux: broken inline asm in tests on<br>
+ mips32-linux<br>
+397012 glibc ld.so uses arch_prctl on i386<br>
+397089 amd64: Incorrect decoding of three-register vmovss/vmovsd opcode 11h<br>
+397354 utimensat should ignore timespec tv_sec if tv_nsec is UTIME_NOW/OMIT<br>
+397424 glibc 2.27 and gdb_server tests<br>
+398028 Assertion `cfsi_fits` failing in simple C program<br>
+398066 s390x: cgijl dep1, 0 reports false unitialised values warning<br>
+<br>
+n-i-bz Fix missing workq_ops operations (macOS)<br>
+n-i-bz fix bug in strspn replacement<br>
+n-i-bz Add support for the Linux BLKFLSBUF ioctl<br>
+n-i-bz Add support for the Linux BLKREPORTZONE and BLKRESETZONE ioctls<br>
+n-i-bz Fix possible stack trashing by semctl syscall wrapping<br>
+n-i-bz Add support for the Linux membarrier() system call<br>
+n-i-bz x86 front end: recognise and handle UD2 correctly<br>
+n-i-bz Signal delivery for x86-linux: ensure that the stack pointer is<br>
+ correctly aligned before entering the handler.<br>
+<br>
+(3.14.0.RC1: 30 September 2018, git c2aeea2d28acb0639bcc8cc1e4ab115067db1eae)<br>
+(3.14.0.RC2: 3 October 2018, git 3e214c4858a6fdd5697e767543a0c19e30505582)<br>
+(3.14.0: 9 October 2018, git 353a3587bb0e2757411f9138f5e936728ed6cc4f)<br>
+<br>
+<br>
+<br>
+Release 3.13.0 (15 June 2017)<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
<br>
3.13.0 is a feature release with many improvements and the usual collection of<br>
Modified: trunk/docs/manual/dist.news.old.html
==============================================================================
--- trunk/docs/manual/dist.news.old.html (original)
+++ trunk/docs/manual/dist.news.old.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>3. OLDER NEWS</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.news.html" title="2. NEWS">
Modified: trunk/docs/manual/dist.readme-android.html
==============================================================================
--- trunk/docs/manual/dist.readme-android.html (original)
+++ trunk/docs/manual/dist.readme-android.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>9. README.android</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.readme-s390.html" title="8. README.S390">
Modified: trunk/docs/manual/dist.readme-developers.html
==============================================================================
--- trunk/docs/manual/dist.readme-developers.html (original)
+++ trunk/docs/manual/dist.readme-developers.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>6. README_DEVELOPERS</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.readme-missing.html" title="5. README_MISSING_SYSCALL_OR_IOCTL">
@@ -174,19 +174,18 @@
(1) Check out 2 trees, "Inner" and "Outer". Inner runs the app<br>
directly. Outer runs Inner.<br>
<br>
-(2) Configure inner with --enable-inner and build/install as usual.<br>
+(2) Configure Inner with --enable-inner and build as usual.<br>
<br>
-(3) Configure Outer normally and build/install as usual.<br>
+(3) Configure Outer normally and build+install as usual.<br>
+ Note: You must use a "make install"-ed valgrind.<br>
+ Do *not* use vg-in-place for the Outer valgrind.<br>
<br>
(4) Choose a very simple program (date) and try<br>
<br>
outer/.../bin/valgrind --sim-hints=enable-outer --trace-children=yes \<br>
--smc-check=all-non-file \<br>
--run-libc-freeres=no --tool=cachegrind -v \<br>
- inner/.../bin/valgrind --vgdb-prefix=./inner --tool=none -v prog<br>
-<br>
-Note: You must use a "make install"-ed valgrind.<br>
-Do *not* use vg-in-place for the outer valgrind.<br>
+ inner/.../vg-in-place --vgdb-prefix=./inner --tool=none -v prog<br>
<br>
If you omit the --trace-children=yes, you'll only monitor Inner's launcher<br>
program, not its stage2. Outer needs --run-libc-freeres=no, as otherwise<br>
@@ -214,12 +213,12 @@
--sim-hints=no-inner-prefix to the Inner to disable the production<br>
of the prefix in the stdout/stderr output of Inner.<br>
<br>
-The allocator (coregrind/m_mallocfree.c) is annotated with client requests<br>
-so Memcheck can be used to find leaks and use after free in an Inner<br>
-Valgrind.<br>
+The allocators in coregrind/m_mallocfree.c and VEX/priv/main_util.h are<br>
+annotated with client requests so Memcheck can be used to find leaks<br>
+and use after free in an Inner Valgrind.<br>
<br>
The Valgrind "big lock" is annotated with helgrind client requests<br>
-so helgrind and drd can be used to find race conditions in an Inner<br>
+so Helgrind and DRD can be used to find race conditions in an Inner<br>
Valgrind.<br>
<br>
All this has not been tested much, so don't be surprised if you hit problems.<br>
Modified: trunk/docs/manual/dist.readme-missing.html
==============================================================================
--- trunk/docs/manual/dist.readme-missing.html (original)
+++ trunk/docs/manual/dist.readme-missing.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>5. README_MISSING_SYSCALL_OR_IOCTL</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.readme.html" title="4. README">
Modified: trunk/docs/manual/dist.readme-packagers.html
==============================================================================
--- trunk/docs/manual/dist.readme-packagers.html (original)
+++ trunk/docs/manual/dist.readme-packagers.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>7. README_PACKAGERS</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.readme-developers.html" title="6. README_DEVELOPERS">
@@ -28,6 +28,9 @@
Thanks for taking the time and effort to make a binary distribution of<br>
Valgrind. The following notes may save you some trouble.<br>
<br>
+-- If your toolchain (compiler, linker) support lto, using the configure<br>
+ option --enable-lto=yes will produce a smaller/faster valgrind<br>
+ (up to 10%).<br>
<br>
-- Do not ship your Linux distro with a completely stripped<br>
/lib/ld.so. At least leave the debugging symbol names on -- line<br>
@@ -51,7 +54,7 @@
not any debuginfo or extra symbols for any other libraries.<br>
<br>
<br>
--- (Unfortunate but true) When you configure to build with the <br>
+-- (Unfortunate but true) When you configure to build with the<br>
--prefix=/foo/bar/xyzzy option, the prefix /foo/bar/xyzzy gets<br>
baked into valgrind. The consequence is that you _must_ install<br>
valgrind at the location specified in the prefix. If you don't,<br>
Modified: trunk/docs/manual/dist.readme-s390.html
==============================================================================
--- trunk/docs/manual/dist.readme-s390.html (original)
+++ trunk/docs/manual/dist.readme-s390.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>8. README.S390</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.readme-packagers.html" title="7. README_PACKAGERS">
Modified: trunk/docs/manual/dist.readme.html
==============================================================================
--- trunk/docs/manual/dist.readme.html (original)
+++ trunk/docs/manual/dist.readme.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>4. README</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="dist.html" title="Valgrind Distribution Documents">
<link rel="prev" href="dist.news.old.html" title="3. OLDER NEWS">
@@ -60,8 +60,8 @@
- PPC32/Linux<br>
- PPC64/Linux<br>
- ARM/Linux<br>
-- x86/MacOSX<br>
-- AMD64/MacOSX<br>
+- x86/macOS<br>
+- AMD64/macOS<br>
- S390X/Linux<br>
- MIPS32/Linux<br>
- MIPS64/Linux<br>
@@ -69,7 +69,7 @@
- AMD64/Solaris<br>
<br>
Note that AMD64 is just another name for x86_64, and Valgrind runs fine<br>
-on Intel processors. Also note that the core of MacOSX is called<br>
+on Intel processors. Also note that the core of macOS is called<br>
"Darwin" and this name is used sometimes.<br>
<br>
Valgrind is licensed under the GNU General Public License, version 2. <br>
@@ -88,9 +88,9 @@
<br>
Building and installing it<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
-To install from the Subversion repository :<br>
+To install from the GIT repository:<br>
<br>
- 0. Check out the code from SVN, following the instructions at<br>
+ 0. Clone the code from GIT, following the instructions at<br>
http://www.valgrind.org/downloads/repository.html.<br>
<br>
1. cd into the source directory.<br>
Modified: trunk/docs/manual/drd-manual.html
==============================================================================
--- trunk/docs/manual/drd-manual.html (original)
+++ trunk/docs/manual/drd-manual.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>8. DRD: a thread error detector</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="hg-manual.html" title="7. Helgrind: a thread error detector">
Modified: trunk/docs/manual/faq.html
==============================================================================
--- trunk/docs/manual/faq.html (original)
+++ trunk/docs/manual/faq.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Valgrind Frequently Asked Questions</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="FAQ.html" title="Valgrind FAQ">
<link rel="prev" href="FAQ.html" title="Valgrind FAQ">
@@ -187,7 +187,7 @@
<tr><td colspan="2"> </td></tr>
<tr class="question">
<td align="left" valign="top">
-<a name="faq.glibc_devel"></a><a name="idm140394923880656"></a><b>2.2.</b>
+<a name="faq.glibc_devel"></a><a name="idm139771381661216"></a><b>2.2.</b>
</td>
<td align="left" valign="top">
<b>When building Valgrind, 'make' fails with this:</b><pre class="screen">
@@ -404,10 +404,12 @@
with <code class="option">-g</code> to add debug information. And don't strip
symbol tables (programs should be unstripped unless you run 'strip'
on them; some libraries ship stripped).</p>
-<p>Also, for leak reports involving shared objects, if the shared
- object is unloaded before the program terminates, Valgrind will
- discard the debug information and the error message will be full of
- <code class="literal">???</code> entries. The workaround here is to avoid
+<p>Also, for leak reports involving shared objects, if the shared object
+ is unloaded before the program terminates, Valgrind will discard the debug
+ information and the error message will be full of <code class="literal">???</code>
+ entries. If you use the option <code class="option">--keep-debuginfo=yes</code>, then
+ Valgrind will keep the debug information in order to show the stack traces,
+ at the price of increased memory. An alternate workaround is to avoid
calling <code class="function">dlclose</code> on these shared objects.</p>
<p>Also, <code class="option">-fomit-frame-pointer</code> and
<code class="option">-fstack-check</code> can make stack traces worse.</p>
Modified: trunk/docs/manual/hg-manual.html
==============================================================================
--- trunk/docs/manual/hg-manual.html (original)
+++ trunk/docs/manual/hg-manual.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>7. Helgrind: a thread error detector</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="cl-manual.html" title="6. Callgrind: a call-graph generating cache and branch prediction profiler">
@@ -1008,6 +1008,58 @@
<code class="option">--history-level=none</code>.</p>
</dd>
<dt>
+<a name="opt.delta-stacktrace"></a><span class="term">
+ <code class="option">--delta-stacktrace=no|yes
+ [default: yes on linux amd64/x86] </code>
+ </span>
+</dt>
+<dd>
+<p>This flag only has any effect
+ at <code class="option">--history-level=full</code>.</p>
+<p><code class="option">--delta-stacktrace</code> configures the way Helgrind
+ captures the stacktraces for the
+ option <code class="option">--history-level=full</code>. Such a stacktrace is
+ typically needed each time a new piece of memory is read or written in a
+ basic block of instructions. </p>
+<p><code class="option">--delta-stacktrace=no</code> causes
+ Helgrind to compute a full history stacktrace from the unwind info
+ each time a stacktrace is needed.</p>
+<p><code class="option">--delta-stacktrace=yes</code> indicates to Helgrind to
+ derive a new stacktrace from the previous stacktrace, as long as there
+ was no call instruction, no return instruction, or any other instruction
+ changing the call stack since the previous stacktrace was captured. If
+ no such instruction was executed, the new stacktrace can be derived from
+ the previous stacktrace by just changing the top frame to the current
+ program counter. This option can speed up Helgrind by 25% when
+ using <code class="option">--history-level=full</code>. </p>
+<p>The following aspects have to be considered when
+ using <code class="option">--delta-stacktrace=yes</code> :
+ </p>
+<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
+<li class="listitem">In some cases (for example in a function prologue), the
+ valgrind unwinder might not properly unwind the stack, due to some
+ limitations and/or due to wrong unwind info. When using
+ --delta-stacktrace=yes, the wrong stack trace captured in the
+ function prologue will be kept till the next call or return.
+ </li>
+<li class="listitem">On the other hand, --delta-stacktrace=yes sometimes helps to
+ obtain a correct stacktrace, for example when the unwind info allows
+ a correct stacktrace to be done in the beginning of the sequence,
+ but not later on in the instruction sequence.</li>
+<li class="listitem">Determining which instructions are changing the callstack is
+ partially based on platform dependent heuristics, which have to be
+ tuned/validated specifically for the platform. Also, unwinding in a
+ function prologue must be good enough to allow using
+ --delta-stacktrace=yes. Currently, the option --delta-stacktrace=yes
+ has been reasonably validated only on linux x86 32 bits and linux
+ amd64 64 bits. For more details about how to validate
+ --delta-stacktrace=yes, see debug option --hg-sanity-flags and the
+ function check_cached_rcec_ok in libhb_core.c.</li>
+</ul></div>
+<p>
+ </p>
+</dd>
+<dt>
<a name="opt.conflict-cache-size"></a><span class="term">
<code class="option">--conflict-cache-size=N
[default: 1000000] </code>
@@ -1172,6 +1224,10 @@
</pre>
</li>
+<li class="listitem"><p><code class="varname">xtmemory [<filename> default xtmemory.kcg.%p.%n]</code>
+ requests Helgrind tool to produce an xtree heap memory report.
+ See <a class="xref" href="manual-core.html#manual-core.xtree" title="2.9. Execution Trees">Execution Trees</a> for
+ a detailed explanation about execution trees. </p></li>
</ul></div>
</div>
<div class="sect1">
Modified: trunk/docs/manual/index.html
==============================================================================
--- trunk/docs/manual/index.html (original)
+++ trunk/docs/manual/index.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Valgrind Documentation</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="next" href="QuickStart.html" title="The Valgrind Quick Start Guide">
</head>
@@ -14,12 +14,12 @@
<div>
<div align="center"><h1 class="title">
<a name="set-index"></a>Valgrind Documentation</h1></div>
-<div align="center"><p class="releaseinfo">Release 3.13.0 15 June 2017</p></div>
-<div align="center"><p class="copyright">Copyright © 2000-2017
+<div align="center"><p class="releaseinfo">Release 3.14.0 9 October 2018</p></div>
+<div align="center"><p class="copyright">Copyright © 2000-2018
<a class="link" href="dist.authors.html" title="1. AUTHORS">AUTHORS</a>
</p></div>
<div align="center"><div class="legalnotice">
-<a name="idm140394938157648"></a><p>Permission is granted to copy, distribute and/or modify
+<a name="idm139771394918400"></a><p>Permission is granted to copy, distribute and/or modify
this document under the terms of the GNU Free Documentation
License, Version 1.2 or any later version published by the
Free Software Foundation; with no Invariant Sections, with no
Modified: trunk/docs/manual/license.gfdl.html
==============================================================================
--- trunk/docs/manual/license.gfdl.html (original)
+++ trunk/docs/manual/license.gfdl.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>2. The GNU Free Documentation License</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="licenses.html" title="GNU Licenses">
<link rel="prev" href="license.gpl.html" title="1. The GNU General Public License">
Modified: trunk/docs/manual/license.gpl.html
==============================================================================
--- trunk/docs/manual/license.gpl.html (original)
+++ trunk/docs/manual/license.gpl.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>1. The GNU General Public License</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="licenses.html" title="GNU Licenses">
<link rel="prev" href="licenses.html" title="GNU Licenses">
Modified: trunk/docs/manual/licenses.html
==============================================================================
--- trunk/docs/manual/licenses.html (original)
+++ trunk/docs/manual/licenses.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>GNU Licenses</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="index.html" title="Valgrind Documentation">
<link rel="prev" href="dist.readme-solaris.html" title="12. README.solaris">
Modified: trunk/docs/manual/lk-manual.html
==============================================================================
--- trunk/docs/manual/lk-manual.html (original)
+++ trunk/docs/manual/lk-manual.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>13. Lackey: an example tool</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="bbv-manual.html" title="12. BBV: an experimental basic block vector generation tool">
Modified: trunk/docs/manual/manual-core-adv.html
==============================================================================
--- trunk/docs/manual/manual-core-adv.html (original)
+++ trunk/docs/manual/manual-core-adv.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>3. Using and understanding the Valgrind core: Advanced Topics</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="manual-core.html" title="2. Using and understanding the Valgrind core">
@@ -355,7 +355,7 @@
<pre class="programlisting">
==2418== Memcheck, a memory error detector
==2418== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
-==2418== Using Valgrind-3.13.0.SVN and LibVEX; rerun with -h for copyright info
+==2418== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright info
==2418== Command: ./prog
==2418==
==2418== (action at startup) vgdb me ...
@@ -1211,7 +1211,7 @@
command line, then set a few breakpoints, set the vgdb-error value
to a huge value and continue execution.</p></li>
<li class="listitem"><p><code class="varname">xtmemory [<filename> default xtmemory.kcg.%p.%n]</code>
- requests the tool to produce an xtree heap memory report.
+ requests the tool (Memcheck, Massif, Helgrind) to produce an xtree heap memory report.
See <a class="xref" href="manual-core.html#manual-core.xtree" title="2.9. Execution Trees">Execution Trees</a> for
a detailed explanation about execution trees. </p></li>
</ul></div>
Modified: trunk/docs/manual/manual-core.html
==============================================================================
--- trunk/docs/manual/manual-core.html (original)
+++ trunk/docs/manual/manual-core.html Tue Oct 16 10:31:06 2018
@@ -3,7 +3,7 @@
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>2. Using and understanding the Valgrind core</title>
<link rel="stylesheet" type="text/css" href="vg_basic.css">
-<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
+<meta name="generator" content="DocBook XSL Stylesheets Vsnapshot">
<link rel="home" href="index.html" title="Valgrind Documentation">
<link rel="up" href="manual.html" title="Valgrind User Manual">
<link rel="prev" href="manual-intro.html" title="1. Introduction">
@@ -369,7 +369,7 @@
it got used, its name and the filename and line number where the suppression is
defined. Depending on the suppression kind, the filename and line number are optionally
followed by additional information (such as the number of blocks and bytes suppressed
-by a memcheck leak suppression). Here's the suppressions used by a
+by a Memcheck leak suppression). Here's the suppressions used by a
run of <code class="computeroutput">valgrind -v --tool=memcheck ls -l</code>:</p>
<pre class="programlisting">
--1610-- used_suppression: 2 dl-hack3-cond-1 /usr/lib/valgrind/default.supp:1234
@@ -414,13 +414,15 @@
<p>Remaining lines: This is the calling context for the error --
the chain of function calls that led to it. There can be up to 24
of these lines.</p>
-<p>Locations may be names of either shared objects or
- functions. They begin
- <code class="computeroutput">obj:</code> and
- <code class="computeroutput">fun:</code> respectively. Function and
- object names to match against may use the wildcard characters
+<p>Locations may be names of either shared objects, functions,
+ or source lines. They begin with
+ <code class="computeroutput">obj:</code>,
+ <code class="computeroutput">fun:</code>, or
+ <code class="computeroutput">src:</code> respectively. Function,
+ object, and file names to match against may use the wildcard characters
<code class="computeroutput">*</code> and
- <code class="computeroutput">?</code>.</p>
+ <code class="computeroutput">?</code>. Source lines are specified
+ using the form <code class="filename">filename[:lineNumber]</code>.</p>
<p><span class="command"><strong>Important note: </strong></span> C++ function names must be
<span class="command"><strong>mangled</strong></span>. If you are writing suppressions by
hand, use the <code class="option">--demangle=no</code> option to get the
@@ -482,9 +484,20 @@
locations is regrettable, but is about all you can hope for, given that
the X11 libraries shipped on the Linux distro on which this example
was made have had their symbol tables removed.</p>
+<p>An example of the src: specification, again for the Memcheck tool:</p>
+<pre class="programlisting">
+{
+ libX11.so.6.2/libX11.so.6.2/libXaw.so.7.0
+ Memcheck:Value4
+ src:valid.c:321
+}</pre>
+<p>This suppresses any size-4 uninitialised-value error which occurs
+at line 321 in <code class="filename">valid.c</code>.</p>
<p>Although the above two examples do not make this clear, you can
-freely mix <code class="computeroutput">obj:</code> and
-<code class="computeroutput">fun:</code> lines in a suppression.</p>
+freely mix <code class="computeroutput">obj:</code>,
+<code class="computeroutput">fun:</code>, and
+<code class="computeroutput">src:</code>
+lines in a suppression.</p>
<p>Finally, here's an example using three frame-level wildcards:</p>
<pre class="programlisting">
{
@@ -1004,6 +1017,16 @@
suite, since it makes it easy to detect test cases for which
Valgrind has reported errors, just by inspecting return codes.</p></dd>
<dt>
+<a name="opt.exit-on-first-error"></a><span class="term">
+ <code class="option">--exit-on-first-error=<yes|no> [default: no] </code>
+ </span>
+</dt>
+<dd><p>If this option is enabled, Valgrind exits on the first error.
+ A nonzero exit value must be defined using
+ <code class="computeroutput">--error-exitcode</code> option.
+ Useful if you are running regression tests or have some other
+ automated test machinery.</p></dd>
+<dt>
<a name="opt.error-markers"></a><span class="term">
<code class="option">--error-markers=<begin>,<end> [default: none]</code>
</span>
@@ -1040,6 +1063,27 @@
that you would otherwise get in such cases.</p>
</dd>
<dt>
+<a name="opt.keep-debuginfo"></a><span class="term">
+ <code class="option">--keep-debuginfo=<yes|no> [default: no] </code>
+ </span>
+</dt>
+<dd>
+<p>When enabled, keep ("archive") symbols and all other debuginfo
+ for unloaded code. This allows saved stack traces to include file/line
+ info for code th...
[truncated message content] |