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
(2) |
2
(9) |
|
3
(1) |
4
|
5
(1) |
6
(3) |
7
(1) |
8
|
9
(3) |
|
10
|
11
(4) |
12
|
13
(24) |
14
(14) |
15
(22) |
16
|
|
17
|
18
(4) |
19
(4) |
20
(3) |
21
|
22
|
23
|
|
24
|
25
(2) |
26
|
27
(2) |
28
|
29
|
30
|
|
31
|
|
|
|
|
|
|
|
From: Mark W. <ma...@so...> - 2020-05-13 16:07:11
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=168dc791467f889a032582ae718d44f9a1811a58 commit 168dc791467f889a032582ae718d44f9a1811a58 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 16:50:21 2020 +0200 cg-manual.xml: Use cg-manual.forkingprograms id, not ms-manual. Diff: --- cachegrind/docs/cg-manual.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cachegrind/docs/cg-manual.xml b/cachegrind/docs/cg-manual.xml index 73b58b634e..353e1dbc6d 100644 --- a/cachegrind/docs/cg-manual.xml +++ b/cachegrind/docs/cg-manual.xml @@ -492,7 +492,7 @@ assembly code source files in the same way as C/C++ source files.</para> </sect2> -<sect2 id="ms-manual.forkingprograms" xreflabel="Forking Programs"> +<sect2 id="cg-manual.forkingprograms" xreflabel="Forking Programs"> <title>Forking Programs</title> <para>If your program forks, the child will inherit all the profiling data that has been gathered for the parent.</para> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:07:06
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=9a79b194f2f41dfdc63fddcd10643005ab1f36dc commit 9a79b194f2f41dfdc63fddcd10643005ab1f36dc Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 16:43:41 2020 +0200 dh-manual.xml: Don't use computeroutput in title. It seems legal docbook, but it crashes our xsltproc/pdfxmltex toolchain. Diff: --- dhat/docs/dh-manual.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index f643e62d63..e1d2ac6141 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -622,7 +622,7 @@ optimization.</para> <sect1 id="dh-manual.realloc" xreflabel="Treatment of realloc"> -<title>Treatment of <computeroutput>realloc</computeroutput></title> +<title>Treatment of realloc</title> <para><computeroutput>realloc</computeroutput> is a tricky function and there are several different ways that DHAT could handle it.</para> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:06:55
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=53dd0183d815a9d1c6eb27e2a79a84127f08c017 commit 53dd0183d815a9d1c6eb27e2a79a84127f08c017 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:52:32 2020 +0200 dh-manual.xml: Put stray text before graphic in a para. Diff: --- dhat/docs/dh-manual.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index f9fef0d505..f643e62d63 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -187,9 +187,10 @@ showing the allocation point (AP) tree.</para> <sect3><title>Structure</title> -The following image shows a screenshot of part of an AP tree. The font is very -small because this screenshot is intended to demonstrate the high-level -structure of the tree rather than the details within the text. +<para>The following image shows a screenshot of part of an AP +tree. The font is very small because this screenshot is intended to +demonstrate the high-level structure of the tree rather than the +details within the text.</para> <graphic fileref="images/dh-tree.png" scalefit="1"/> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:06:48
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=8fe1344c1105b8da94fdbc7c8b044514e10194b1 commit 8fe1344c1105b8da94fdbc7c8b044514e10194b1 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:49:31 2020 +0200 ms-manual.xml: Put stray ':' inside para. Diff: --- massif/docs/ms-manual.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/massif/docs/ms-manual.xml b/massif/docs/ms-manual.xml index cc99025cbe..f8637de807 100644 --- a/massif/docs/ms-manual.xml +++ b/massif/docs/ms-manual.xml @@ -611,7 +611,7 @@ says: (page allocation syscalls) mmap/mremap/brk, --alloc-fns, etc. ]]></screen> -<para>instead of the usual</para>: +<para>instead of the usual:</para> <screen><![CDATA[ (heap allocation functions) malloc/new/new[], --alloc-fns, etc. |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:06:41
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=47660cc83d93d772da7570de7368f1f92d52d3e6 commit 47660cc83d93d772da7570de7368f1f92d52d3e6 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:46:16 2020 +0200 manual-core-adv.xml: listitems contain paras, not plain CDATA. Diff: --- docs/xml/manual-core-adv.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/xml/manual-core-adv.xml b/docs/xml/manual-core-adv.xml index e94a402b6a..fd05ecf2ec 100644 --- a/docs/xml/manual-core-adv.xml +++ b/docs/xml/manual-core-adv.xml @@ -841,15 +841,15 @@ are however some limitations and peculiarities:</para> the precision of registers and flags values (a typical performance impact for memcheck is given for each option). <itemizedlist> - <listitem> + <listitem><para> <option>--vex-iropt-register-updates=allregs-at-mem-access</option> (+10%) ensures that all registers and flags are up to date at each memory access. - </listitem> - <listitem> + </para></listitem> + <listitem><para> <option>--vex-iropt-register-updates=allregs-at-each-insn</option> (+25%) ensures that all registers and flags are up to date at each instruction. - </listitem> + </para></listitem> </itemizedlist> Note that <option>--vgdb=full</option> (+500%, see above Precision of "stop-at" commands) automatically |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:06:34
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=014bcea452ec8dc7a547f5a7307482eac1db458d commit 014bcea452ec8dc7a547f5a7307482eac1db458d Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:37:13 2020 +0200 manual-core.xml: Fix various xmllint issues. Wrap bare CDATA text in a para and make sure that all listitems contain paras. Diff: --- docs/xml/manual-core.xml | 50 ++++++++++++++++++++++++------------------------ 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml index 50904ff82a..b36009ed90 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -578,13 +578,13 @@ lines in a suppression.</para> fun:main } ]]></programlisting> -This suppresses Memcheck memory-leak errors, in the case where +<para>This suppresses Memcheck memory-leak errors, in the case where the allocation was done by <computeroutput>main</computeroutput> calling (though any number of intermediaries, including zero) <computeroutput>ccc</computeroutput>, calling onwards via <computeroutput>ddd</computeroutput> and eventually -to <computeroutput>malloc.</computeroutput>. +to <computeroutput>malloc.</computeroutput>.</para> </sect1> @@ -2646,35 +2646,35 @@ PROGRESS: U 130s, W 134s, 97.0% CPU, EvC 574.90M, TIn 657.5k, TOut 3.0k, #thr 63 ]]></programlisting> Each line shows: <itemizedlist> - <listitem><varname>U</varname>: total user time</listitem> - <listitem><varname>W</varname>: total wallclock time</listitem> - <listitem><varname>CPU</varname>: overall average cpu use</listitem> - <listitem><varname>EvC</varname>: number of event checks. An event + <listitem><para><varname>U</varname>: total user time</para></listitem> + <listitem><para><varname>W</varname>: total wallclock time</para></listitem> + <listitem><para><varname>CPU</varname>: overall average cpu use</para></listitem> + <listitem><para><varname>EvC</varname>: number of event checks. An event check is a backwards branch in the simulated program, so this is a - measure of forward progress of the program</listitem> - <listitem><varname>TIn</varname>: number of code blocks instrumented - by the JIT</listitem> - <listitem><varname>TOut</varname>: number of instrumented code - blocks that have been thrown away</listitem> - <listitem><varname>#thr</varname>: number of threads in the - program</listitem> + measure of forward progress of the program</para></listitem> + <listitem><para><varname>TIn</varname>: number of code blocks instrumented + by the JIT</para></listitem> + <listitem><para><varname>TOut</varname>: number of instrumented code + blocks that have been thrown away</para></listitem> + <listitem><para><varname>#thr</varname>: number of threads in the + program</para></listitem> </itemizedlist> From the progress of these, it is possible to observe: <itemizedlist> - <listitem>when the program is compute bound (<varname>TIn</varname> - rises slowly, <varname>EvC</varname> rises rapidly)</listitem> - <listitem>when the program is in a spinloop + <listitem><para>when the program is compute bound (<varname>TIn</varname> + rises slowly, <varname>EvC</varname> rises rapidly)</para></listitem> + <listitem><para>when the program is in a spinloop (<varname>TIn</varname>/<varname>TOut</varname> - fixed, <varname>EvC</varname> rises rapidly)</listitem> - <listitem>when the program is JIT-bound (<varname>TIn</varname> - rises rapidly)</listitem> - <listitem>when the program is rapidly discarding code - (<varname>TOut</varname> rises rapidly)</listitem> - <listitem>when the program is about to achieve some expected state + fixed, <varname>EvC</varname> rises rapidly)</para></listitem> + <listitem><para>when the program is JIT-bound (<varname>TIn</varname> + rises rapidly)</para></listitem> + <listitem><para>when the program is rapidly discarding code + (<varname>TOut</varname> rises rapidly)</para></listitem> + <listitem><para>when the program is about to achieve some expected state (<varname>EvC</varname> arrives at some value you - expect)</listitem> - <listitem> when the program is idling (<varname>U</varname> rises - more slowly than <varname>W</varname>)</listitem> + expect)</para></listitem> + <listitem><para> when the program is idling (<varname>U</varname> rises + more slowly than <varname>W</varname>)</para></listitem> </itemizedlist> </para> </listitem> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:06:20
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=9e87b109a0538228261c215d577a859ae8654bdb commit 9e87b109a0538228261c215d577a859ae8654bdb Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:27:57 2020 +0200 valgrind-manpage.xml: arg cannot contain a program, use replaceable. Diff: --- docs/xml/valgrind-manpage.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/xml/valgrind-manpage.xml b/docs/xml/valgrind-manpage.xml index 332ca4884c..10decc258a 100644 --- a/docs/xml/valgrind-manpage.xml +++ b/docs/xml/valgrind-manpage.xml @@ -21,7 +21,7 @@ <cmdsynopsis> <command>valgrind</command> <arg><replaceable>valgrind-options</replaceable></arg> - <arg><command>your-program</command></arg> + <arg><replaceable>your-program</replaceable></arg> <arg><replaceable>your-program-options</replaceable></arg> </cmdsynopsis> </refsynopsisdiv> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:06:12
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=8e40553f72ca5a95e25d412eec08bdd63045aa3b commit 8e40553f72ca5a95e25d412eec08bdd63045aa3b Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:26:53 2020 +0200 hg-manual.xml: listitems contain paras, not CDATA. Diff: --- helgrind/docs/hg-manual.xml | 42 +++++++++++++++++++++++------------------- 1 file changed, 23 insertions(+), 19 deletions(-) diff --git a/helgrind/docs/hg-manual.xml b/helgrind/docs/hg-manual.xml index 8a1d9166aa..887a4be519 100644 --- a/helgrind/docs/hg-manual.xml +++ b/helgrind/docs/hg-manual.xml @@ -1178,25 +1178,29 @@ unlock(mx) unlock(mx) <para>The following aspects have to be considered when using <option>--delta-stacktrace=yes</option> : <itemizedlist> - <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. - </listitem> - <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.</listitem> - <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.</listitem> + <listitem><para>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. + </para></listitem> + <listitem><para>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.</para></listitem> + <listitem><para>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.</para></listitem> </itemizedlist> </para> </listitem> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:06:05
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=47c44f6c095a4a4ad8149307c499819119aaf053 commit 47c44f6c095a4a4ad8149307c499819119aaf053 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:24:31 2020 +0200 mc-manual.xml: varlistentries cannot contain paras, listitems do. Diff: --- memcheck/docs/mc-manual.xml | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml index 0e7ec4d072..5d6031376c 100644 --- a/memcheck/docs/mc-manual.xml +++ b/memcheck/docs/mc-manual.xml @@ -842,15 +842,14 @@ is <option>--errors-for-leak-kinds=definite,possible</option> <listitem><para><option>none</option> for the empty set.</para> </listitem> </itemizedlist> + <para>Note that these heuristics are dependent on the layout of + the objects produced by the C++ compiler. They have been + tested with some gcc versions (e.g. 4.4 and 4.7). They might + not work properly with other C++ compilers. + </para> </listitem> - - <para>Note that these heuristics are dependent on the layout of the objects - produced by the C++ compiler. They have been tested with some gcc versions - (e.g. 4.4 and 4.7). They might not work properly with other C++ compilers. - </para> </varlistentry> - <varlistentry id="opt.show-reachable" xreflabel="--show-reachable"> <term> <option><![CDATA[--show-reachable=<yes|no> ]]></option> @@ -881,9 +880,10 @@ is <option>--errors-for-leak-kinds=definite,possible</option> </para> </listitem> </itemizedlist> + <para> Note that <option>--show-possibly-lost=no</option> has no + effect if <option>--show-reachable=yes</option> is + specified.</para> </listitem> - <para> Note that <option>--show-possibly-lost=no</option> has no effect - if <option>--show-reachable=yes</option> is specified.</para> </varlistentry> <varlistentry id="opt.xtree-leak" xreflabel="--xtree-leak"> @@ -1399,14 +1399,15 @@ leak kinds are matched by this suppression entry. same way as with the option <option>--show-leak-kinds</option>, that is, one of the following:</para> <itemizedlist> - <listitem>a comma separated list of one or more of - <option>definite indirect possible reachable</option>. + <listitem><para>a comma separated list of one or more of + <option>definite indirect possible reachable</option>.</para> </listitem> - <listitem><option>all</option> to specify the complete set (all leak kinds). + <listitem><para><option>all</option> to specify the complete set + (all leak kinds).</para> </listitem> - <listitem><option>none</option> for the empty set. + <listitem><para><option>none</option> for the empty set.</para> </listitem> </itemizedlist> <para>If this optional extra line is not present, the suppression |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:05:58
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=7425c1bc9678b06cd9552b99e7b397b76d6d2640 commit 7425c1bc9678b06cd9552b99e7b397b76d6d2640 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:13:18 2020 +0200 dh-manual.xml: Remove duplicate dh-manual.options id. Rename one to dh-manual.realloc. Diff: --- dhat/docs/dh-manual.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index bd318f563e..f9fef0d505 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -620,7 +620,7 @@ optimization.</para> </sect1> -<sect1 id="dh-manual.options" xreflabel="Treatment of realloc"> +<sect1 id="dh-manual.realloc" xreflabel="Treatment of realloc"> <title>Treatment of <computeroutput>realloc</computeroutput></title> <para><computeroutput>realloc</computeroutput> is a tricky function and there |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:05:51
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=14c818557cd5d89894818c8503b089adfdbff70a commit 14c818557cd5d89894818c8503b089adfdbff70a Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 14:08:19 2020 +0200 Make manual-writing-tools.xml xmllint clean. Diff: --- docs/xml/manual-writing-tools.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/xml/manual-writing-tools.xml b/docs/xml/manual-writing-tools.xml index 63bc197af7..a36d775544 100644 --- a/docs/xml/manual-writing-tools.xml +++ b/docs/xml/manual-writing-tools.xml @@ -7,8 +7,8 @@ <chapter id="manual-writing-tools" xreflabel="Writing a New Valgrind Tool"> <title>Writing a New Valgrind Tool</title> -So you want to write a Valgrind tool? Here are some instructions that may -help. +<para>So you want to write a Valgrind tool? Here are some instructions +that may help.</para> <sect1 id="manual-writing-tools.intro" xreflabel="Introduction"> <title>Introduction</title> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:05:44
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=ec37306c12f38d38b7f5e5f365ed011cf2702089 commit ec37306c12f38d38b7f5e5f365ed011cf2702089 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 14:03:27 2020 +0200 Make FAQ.xml xmllint clean. Diff: --- docs/xml/FAQ.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml index b124606282..9919c8d40c 100644 --- a/docs/xml/FAQ.xml +++ b/docs/xml/FAQ.xml @@ -401,7 +401,7 @@ Invalid write of size 1 nature of the way Valgrind works that it cannot exactly replicate a native execution environment. In the case where your program crashes due to a memory error when run natively but not when run under Valgrind, - in most cases Memcheck should identify the bad memory operation.</para>. + in most cases Memcheck should identify the bad memory operation.</para> </answer> </qandaentry> @@ -629,7 +629,7 @@ is built standalone as FAQ.txt. That's why we link to, for example, the online copy of the manual. --> <qandaentry id="e-help"> - <!-- <question><para/></question> --> + <question><para>Where can I get more help?</para></question> <answer id="a-help"> <para>Read the appropriate section(s) of the <ulink url="&vg-docs-url;">Valgrind Documentation</ulink>.</para> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:00:39
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=168dc791467f889a032582ae718d44f9a1811a58 commit 168dc791467f889a032582ae718d44f9a1811a58 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 16:50:21 2020 +0200 cg-manual.xml: Use cg-manual.forkingprograms id, not ms-manual. Diff: --- cachegrind/docs/cg-manual.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cachegrind/docs/cg-manual.xml b/cachegrind/docs/cg-manual.xml index 73b58b634e..353e1dbc6d 100644 --- a/cachegrind/docs/cg-manual.xml +++ b/cachegrind/docs/cg-manual.xml @@ -492,7 +492,7 @@ assembly code source files in the same way as C/C++ source files.</para> </sect2> -<sect2 id="ms-manual.forkingprograms" xreflabel="Forking Programs"> +<sect2 id="cg-manual.forkingprograms" xreflabel="Forking Programs"> <title>Forking Programs</title> <para>If your program forks, the child will inherit all the profiling data that has been gathered for the parent.</para> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:00:32
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=9a79b194f2f41dfdc63fddcd10643005ab1f36dc commit 9a79b194f2f41dfdc63fddcd10643005ab1f36dc Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 16:43:41 2020 +0200 dh-manual.xml: Don't use computeroutput in title. It seems legal docbook, but it crashes our xsltproc/pdfxmltex toolchain. Diff: --- dhat/docs/dh-manual.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index f643e62d63..e1d2ac6141 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -622,7 +622,7 @@ optimization.</para> <sect1 id="dh-manual.realloc" xreflabel="Treatment of realloc"> -<title>Treatment of <computeroutput>realloc</computeroutput></title> +<title>Treatment of realloc</title> <para><computeroutput>realloc</computeroutput> is a tricky function and there are several different ways that DHAT could handle it.</para> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:00:18
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=53dd0183d815a9d1c6eb27e2a79a84127f08c017 commit 53dd0183d815a9d1c6eb27e2a79a84127f08c017 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:52:32 2020 +0200 dh-manual.xml: Put stray text before graphic in a para. Diff: --- dhat/docs/dh-manual.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index f9fef0d505..f643e62d63 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -187,9 +187,10 @@ showing the allocation point (AP) tree.</para> <sect3><title>Structure</title> -The following image shows a screenshot of part of an AP tree. The font is very -small because this screenshot is intended to demonstrate the high-level -structure of the tree rather than the details within the text. +<para>The following image shows a screenshot of part of an AP +tree. The font is very small because this screenshot is intended to +demonstrate the high-level structure of the tree rather than the +details within the text.</para> <graphic fileref="images/dh-tree.png" scalefit="1"/> |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:00:16
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=8fe1344c1105b8da94fdbc7c8b044514e10194b1 commit 8fe1344c1105b8da94fdbc7c8b044514e10194b1 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:49:31 2020 +0200 ms-manual.xml: Put stray ':' inside para. Diff: --- massif/docs/ms-manual.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/massif/docs/ms-manual.xml b/massif/docs/ms-manual.xml index cc99025cbe..f8637de807 100644 --- a/massif/docs/ms-manual.xml +++ b/massif/docs/ms-manual.xml @@ -611,7 +611,7 @@ says: (page allocation syscalls) mmap/mremap/brk, --alloc-fns, etc. ]]></screen> -<para>instead of the usual</para>: +<para>instead of the usual:</para> <screen><![CDATA[ (heap allocation functions) malloc/new/new[], --alloc-fns, etc. |
|
From: Mark W. <ma...@so...> - 2020-05-13 16:00:04
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=47660cc83d93d772da7570de7368f1f92d52d3e6 commit 47660cc83d93d772da7570de7368f1f92d52d3e6 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:46:16 2020 +0200 manual-core-adv.xml: listitems contain paras, not plain CDATA. Diff: --- docs/xml/manual-core-adv.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/xml/manual-core-adv.xml b/docs/xml/manual-core-adv.xml index e94a402b6a..fd05ecf2ec 100644 --- a/docs/xml/manual-core-adv.xml +++ b/docs/xml/manual-core-adv.xml @@ -841,15 +841,15 @@ are however some limitations and peculiarities:</para> the precision of registers and flags values (a typical performance impact for memcheck is given for each option). <itemizedlist> - <listitem> + <listitem><para> <option>--vex-iropt-register-updates=allregs-at-mem-access</option> (+10%) ensures that all registers and flags are up to date at each memory access. - </listitem> - <listitem> + </para></listitem> + <listitem><para> <option>--vex-iropt-register-updates=allregs-at-each-insn</option> (+25%) ensures that all registers and flags are up to date at each instruction. - </listitem> + </para></listitem> </itemizedlist> Note that <option>--vgdb=full</option> (+500%, see above Precision of "stop-at" commands) automatically |
|
From: Mark W. <ma...@so...> - 2020-05-13 15:59:50
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=014bcea452ec8dc7a547f5a7307482eac1db458d commit 014bcea452ec8dc7a547f5a7307482eac1db458d Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:37:13 2020 +0200 manual-core.xml: Fix various xmllint issues. Wrap bare CDATA text in a para and make sure that all listitems contain paras. Diff: --- docs/xml/manual-core.xml | 50 ++++++++++++++++++++++++------------------------ 1 file changed, 25 insertions(+), 25 deletions(-) diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml index 50904ff82a..b36009ed90 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -578,13 +578,13 @@ lines in a suppression.</para> fun:main } ]]></programlisting> -This suppresses Memcheck memory-leak errors, in the case where +<para>This suppresses Memcheck memory-leak errors, in the case where the allocation was done by <computeroutput>main</computeroutput> calling (though any number of intermediaries, including zero) <computeroutput>ccc</computeroutput>, calling onwards via <computeroutput>ddd</computeroutput> and eventually -to <computeroutput>malloc.</computeroutput>. +to <computeroutput>malloc.</computeroutput>.</para> </sect1> @@ -2646,35 +2646,35 @@ PROGRESS: U 130s, W 134s, 97.0% CPU, EvC 574.90M, TIn 657.5k, TOut 3.0k, #thr 63 ]]></programlisting> Each line shows: <itemizedlist> - <listitem><varname>U</varname>: total user time</listitem> - <listitem><varname>W</varname>: total wallclock time</listitem> - <listitem><varname>CPU</varname>: overall average cpu use</listitem> - <listitem><varname>EvC</varname>: number of event checks. An event + <listitem><para><varname>U</varname>: total user time</para></listitem> + <listitem><para><varname>W</varname>: total wallclock time</para></listitem> + <listitem><para><varname>CPU</varname>: overall average cpu use</para></listitem> + <listitem><para><varname>EvC</varname>: number of event checks. An event check is a backwards branch in the simulated program, so this is a - measure of forward progress of the program</listitem> - <listitem><varname>TIn</varname>: number of code blocks instrumented - by the JIT</listitem> - <listitem><varname>TOut</varname>: number of instrumented code - blocks that have been thrown away</listitem> - <listitem><varname>#thr</varname>: number of threads in the - program</listitem> + measure of forward progress of the program</para></listitem> + <listitem><para><varname>TIn</varname>: number of code blocks instrumented + by the JIT</para></listitem> + <listitem><para><varname>TOut</varname>: number of instrumented code + blocks that have been thrown away</para></listitem> + <listitem><para><varname>#thr</varname>: number of threads in the + program</para></listitem> </itemizedlist> From the progress of these, it is possible to observe: <itemizedlist> - <listitem>when the program is compute bound (<varname>TIn</varname> - rises slowly, <varname>EvC</varname> rises rapidly)</listitem> - <listitem>when the program is in a spinloop + <listitem><para>when the program is compute bound (<varname>TIn</varname> + rises slowly, <varname>EvC</varname> rises rapidly)</para></listitem> + <listitem><para>when the program is in a spinloop (<varname>TIn</varname>/<varname>TOut</varname> - fixed, <varname>EvC</varname> rises rapidly)</listitem> - <listitem>when the program is JIT-bound (<varname>TIn</varname> - rises rapidly)</listitem> - <listitem>when the program is rapidly discarding code - (<varname>TOut</varname> rises rapidly)</listitem> - <listitem>when the program is about to achieve some expected state + fixed, <varname>EvC</varname> rises rapidly)</para></listitem> + <listitem><para>when the program is JIT-bound (<varname>TIn</varname> + rises rapidly)</para></listitem> + <listitem><para>when the program is rapidly discarding code + (<varname>TOut</varname> rises rapidly)</para></listitem> + <listitem><para>when the program is about to achieve some expected state (<varname>EvC</varname> arrives at some value you - expect)</listitem> - <listitem> when the program is idling (<varname>U</varname> rises - more slowly than <varname>W</varname>)</listitem> + expect)</para></listitem> + <listitem><para> when the program is idling (<varname>U</varname> rises + more slowly than <varname>W</varname>)</para></listitem> </itemizedlist> </para> </listitem> |
|
From: Mark W. <ma...@so...> - 2020-05-13 15:59:43
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=9e87b109a0538228261c215d577a859ae8654bdb commit 9e87b109a0538228261c215d577a859ae8654bdb Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:27:57 2020 +0200 valgrind-manpage.xml: arg cannot contain a program, use replaceable. Diff: --- docs/xml/valgrind-manpage.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/xml/valgrind-manpage.xml b/docs/xml/valgrind-manpage.xml index 332ca4884c..10decc258a 100644 --- a/docs/xml/valgrind-manpage.xml +++ b/docs/xml/valgrind-manpage.xml @@ -21,7 +21,7 @@ <cmdsynopsis> <command>valgrind</command> <arg><replaceable>valgrind-options</replaceable></arg> - <arg><command>your-program</command></arg> + <arg><replaceable>your-program</replaceable></arg> <arg><replaceable>your-program-options</replaceable></arg> </cmdsynopsis> </refsynopsisdiv> |
|
From: Mark W. <ma...@so...> - 2020-05-13 15:59:36
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=8e40553f72ca5a95e25d412eec08bdd63045aa3b commit 8e40553f72ca5a95e25d412eec08bdd63045aa3b Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:26:53 2020 +0200 hg-manual.xml: listitems contain paras, not CDATA. Diff: --- helgrind/docs/hg-manual.xml | 42 +++++++++++++++++++++++------------------- 1 file changed, 23 insertions(+), 19 deletions(-) diff --git a/helgrind/docs/hg-manual.xml b/helgrind/docs/hg-manual.xml index 8a1d9166aa..887a4be519 100644 --- a/helgrind/docs/hg-manual.xml +++ b/helgrind/docs/hg-manual.xml @@ -1178,25 +1178,29 @@ unlock(mx) unlock(mx) <para>The following aspects have to be considered when using <option>--delta-stacktrace=yes</option> : <itemizedlist> - <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. - </listitem> - <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.</listitem> - <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.</listitem> + <listitem><para>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. + </para></listitem> + <listitem><para>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.</para></listitem> + <listitem><para>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.</para></listitem> </itemizedlist> </para> </listitem> |
|
From: Mark W. <ma...@so...> - 2020-05-13 15:59:29
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=47c44f6c095a4a4ad8149307c499819119aaf053 commit 47c44f6c095a4a4ad8149307c499819119aaf053 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:24:31 2020 +0200 mc-manual.xml: varlistentries cannot contain paras, listitems do. Diff: --- memcheck/docs/mc-manual.xml | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml index 0e7ec4d072..5d6031376c 100644 --- a/memcheck/docs/mc-manual.xml +++ b/memcheck/docs/mc-manual.xml @@ -842,15 +842,14 @@ is <option>--errors-for-leak-kinds=definite,possible</option> <listitem><para><option>none</option> for the empty set.</para> </listitem> </itemizedlist> + <para>Note that these heuristics are dependent on the layout of + the objects produced by the C++ compiler. They have been + tested with some gcc versions (e.g. 4.4 and 4.7). They might + not work properly with other C++ compilers. + </para> </listitem> - - <para>Note that these heuristics are dependent on the layout of the objects - produced by the C++ compiler. They have been tested with some gcc versions - (e.g. 4.4 and 4.7). They might not work properly with other C++ compilers. - </para> </varlistentry> - <varlistentry id="opt.show-reachable" xreflabel="--show-reachable"> <term> <option><![CDATA[--show-reachable=<yes|no> ]]></option> @@ -881,9 +880,10 @@ is <option>--errors-for-leak-kinds=definite,possible</option> </para> </listitem> </itemizedlist> + <para> Note that <option>--show-possibly-lost=no</option> has no + effect if <option>--show-reachable=yes</option> is + specified.</para> </listitem> - <para> Note that <option>--show-possibly-lost=no</option> has no effect - if <option>--show-reachable=yes</option> is specified.</para> </varlistentry> <varlistentry id="opt.xtree-leak" xreflabel="--xtree-leak"> @@ -1399,14 +1399,15 @@ leak kinds are matched by this suppression entry. same way as with the option <option>--show-leak-kinds</option>, that is, one of the following:</para> <itemizedlist> - <listitem>a comma separated list of one or more of - <option>definite indirect possible reachable</option>. + <listitem><para>a comma separated list of one or more of + <option>definite indirect possible reachable</option>.</para> </listitem> - <listitem><option>all</option> to specify the complete set (all leak kinds). + <listitem><para><option>all</option> to specify the complete set + (all leak kinds).</para> </listitem> - <listitem><option>none</option> for the empty set. + <listitem><para><option>none</option> for the empty set.</para> </listitem> </itemizedlist> <para>If this optional extra line is not present, the suppression |
|
From: Mark W. <ma...@so...> - 2020-05-13 15:59:22
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=7425c1bc9678b06cd9552b99e7b397b76d6d2640 commit 7425c1bc9678b06cd9552b99e7b397b76d6d2640 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 15:13:18 2020 +0200 dh-manual.xml: Remove duplicate dh-manual.options id. Rename one to dh-manual.realloc. Diff: --- dhat/docs/dh-manual.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index bd318f563e..f9fef0d505 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -620,7 +620,7 @@ optimization.</para> </sect1> -<sect1 id="dh-manual.options" xreflabel="Treatment of realloc"> +<sect1 id="dh-manual.realloc" xreflabel="Treatment of realloc"> <title>Treatment of <computeroutput>realloc</computeroutput></title> <para><computeroutput>realloc</computeroutput> is a tricky function and there |
|
From: Mark W. <ma...@so...> - 2020-05-13 15:59:15
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=14c818557cd5d89894818c8503b089adfdbff70a commit 14c818557cd5d89894818c8503b089adfdbff70a Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 14:08:19 2020 +0200 Make manual-writing-tools.xml xmllint clean. Diff: --- docs/xml/manual-writing-tools.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/xml/manual-writing-tools.xml b/docs/xml/manual-writing-tools.xml index 63bc197af7..a36d775544 100644 --- a/docs/xml/manual-writing-tools.xml +++ b/docs/xml/manual-writing-tools.xml @@ -7,8 +7,8 @@ <chapter id="manual-writing-tools" xreflabel="Writing a New Valgrind Tool"> <title>Writing a New Valgrind Tool</title> -So you want to write a Valgrind tool? Here are some instructions that may -help. +<para>So you want to write a Valgrind tool? Here are some instructions +that may help.</para> <sect1 id="manual-writing-tools.intro" xreflabel="Introduction"> <title>Introduction</title> |
|
From: Mark W. <ma...@so...> - 2020-05-13 15:59:01
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=ec37306c12f38d38b7f5e5f365ed011cf2702089 commit ec37306c12f38d38b7f5e5f365ed011cf2702089 Author: Mark Wielaard <ma...@kl...> Date: Wed May 13 14:03:27 2020 +0200 Make FAQ.xml xmllint clean. Diff: --- docs/xml/FAQ.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml index b124606282..9919c8d40c 100644 --- a/docs/xml/FAQ.xml +++ b/docs/xml/FAQ.xml @@ -401,7 +401,7 @@ Invalid write of size 1 nature of the way Valgrind works that it cannot exactly replicate a native execution environment. In the case where your program crashes due to a memory error when run natively but not when run under Valgrind, - in most cases Memcheck should identify the bad memory operation.</para>. + in most cases Memcheck should identify the bad memory operation.</para> </answer> </qandaentry> @@ -629,7 +629,7 @@ is built standalone as FAQ.txt. That's why we link to, for example, the online copy of the manual. --> <qandaentry id="e-help"> - <!-- <question><para/></question> --> + <question><para>Where can I get more help?</para></question> <answer id="a-help"> <para>Read the appropriate section(s) of the <ulink url="&vg-docs-url;">Valgrind Documentation</ulink>.</para> |