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
(3) |
|
2
(8) |
3
(19) |
4
(24) |
5
(23) |
6
(16) |
7
(33) |
8
(5) |
|
9
(4) |
10
(23) |
11
(22) |
12
(40) |
13
(30) |
14
(31) |
15
(17) |
|
16
(18) |
17
(20) |
18
(41) |
19
(36) |
20
(25) |
21
(8) |
22
(9) |
|
23
(17) |
24
(12) |
25
(15) |
26
(15) |
27
(16) |
28
(22) |
29
(6) |
|
30
(7) |
31
(10) |
|
|
|
|
|
|
From: <sv...@va...> - 2009-08-10 19:39:10
|
Author: sewardj
Date: 2009-08-10 20:39:02 +0100 (Mon, 10 Aug 2009)
New Revision: 10771
Log:
Fix some const stuff that gcc-4.4.0 complains about.
Modified:
trunk/coregrind/m_redir.c
Modified: trunk/coregrind/m_redir.c
===================================================================
--- trunk/coregrind/m_redir.c 2009-08-10 18:59:54 UTC (rev 10770)
+++ trunk/coregrind/m_redir.c 2009-08-10 19:39:02 UTC (rev 10771)
@@ -223,9 +223,9 @@
HChar* from_fnpatt; /* from fnname pattern */
Addr to_addr; /* where redirecting to */
Bool isWrap; /* wrap or replacement? */
- HChar** mandatory; /* non-NULL ==> abort V and print the
- strings if from_sopatt is loaded but
- from_fnpatt cannot be found */
+ const HChar** mandatory; /* non-NULL ==> abort V and print the
+ strings if from_sopatt is loaded but
+ from_fnpatt cannot be found */
/* VARIABLE PARTS -- used transiently whilst processing redirections */
Bool mark; /* set if spec requires further processing */
Bool done; /* set if spec was successfully matched */
@@ -555,7 +555,7 @@
break;
}
if (sp) {
- HChar** strp;
+ const HChar** strp;
HChar* v = "valgrind: ";
vg_assert(sp->mark);
vg_assert(!sp->done);
@@ -813,7 +813,7 @@
__attribute__((unused)) /* not used on all platforms */
static void add_hardwired_spec ( HChar* sopatt, HChar* fnpatt,
Addr to_addr,
- HChar** mandatory )
+ const HChar** mandatory )
{
Spec* spec = dinfo_zalloc("redir.ahs.1", sizeof(Spec));
vg_assert(spec);
|
|
From: <sv...@va...> - 2009-08-10 19:00:07
|
Author: sewardj
Date: 2009-08-10 19:59:54 +0100 (Mon, 10 Aug 2009)
New Revision: 10770
Log:
parse_type_DIE: push incomplete structure tyents on the type stack,
since gcc-4.4 on Fedora 11 will create DW_TAG_member entries within
it, and we need to have a plausible parent type on the stack.
Modified:
trunk/coregrind/m_debuginfo/readdwarf3.c
Modified: trunk/coregrind/m_debuginfo/readdwarf3.c
===================================================================
--- trunk/coregrind/m_debuginfo/readdwarf3.c 2009-08-10 14:13:12 UTC (rev 10769)
+++ trunk/coregrind/m_debuginfo/readdwarf3.c 2009-08-10 18:59:54 UTC (rev 10770)
@@ -2307,6 +2307,14 @@
if (typeE.Te.TyStOrUn.name == NULL)
goto bad_DIE;
typeE.Te.TyStOrUn.complete = False;
+ /* JRS 2009 Aug 10: <possible kludge>? */
+ /* Push this tyent on the stack, even though it's incomplete.
+ It appears that gcc-4.4 on Fedora 11 will sometimes create
+ DW_TAG_member entries for it, and so we need to have a
+ plausible parent present in order for that to work. See
+ #200029 comments 8 and 9. */
+ typestack_push( cc, parser, td3, &typeE, level );
+ /* </possible kludge> */
goto acquire_Type;
}
if ((!is_decl) /* && (!is_spec) */) {
|
|
From: Nicholas N. <n.n...@gm...> - 2009-08-10 17:21:53
|
Nightly build on ocean32 ( Ubuntu 9.04, x86_64 (32-bit only) )
Started at 2009-08-11 03:00:01 EST
Ended at 2009-08-11 03:21:36 EST
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 483 tests, 9 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
none/tests/empty-exe (stderr)
none/tests/shell (stdout)
none/tests/shell (stderr)
none/tests/shell_valid1 (stderr)
none/tests/shell_valid2 (stderr)
none/tests/shell_valid3 (stderr)
none/tests/shell_zerolength (stderr)
helgrind/tests/tc06_two_races_xml (stderr)
exp-ptrcheck/tests/supp (stderr)
=================================================
== Results from 24 hours ago ==
=================================================
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 482 tests, 9 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
none/tests/empty-exe (stderr)
none/tests/shell (stdout)
none/tests/shell (stderr)
none/tests/shell_valid1 (stderr)
none/tests/shell_valid2 (stderr)
none/tests/shell_valid3 (stderr)
none/tests/shell_zerolength (stderr)
helgrind/tests/tc06_two_races_xml (stderr)
exp-ptrcheck/tests/supp (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Tue Aug 11 03:11:09 2009
--- new.short Tue Aug 11 03:21:36 2009
***************
*** 8,10 ****
! == 482 tests, 9 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
--- 8,10 ----
! == 483 tests, 9 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/origin5-bz2 (stderr)
=================================================
./valgrind-new/exp-ptrcheck/tests/supp.stderr.diff
=================================================
--- supp.stderr.exp 2009-08-11 03:11:29.000000000 +1000
+++ supp.stderr.out 2009-08-11 03:21:32.000000000 +1000
@@ -1,7 +1,7 @@
Syscall param write(buf) is non-contiguous
- at 0x........: write (in /...libc...)
- by 0x........: main (supp.c:16)
+ at 0x........: ??? (in /lib32/ld-2.9.so)
+ by 0x........: (below main)
First byte (0x........) is 3 bytes inside a 6-byte block alloc'd
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: main (supp.c:12)
=================================================
./valgrind-new/helgrind/tests/tc06_two_races_xml.stderr.diff
=================================================
--- tc06_two_races_xml.stderr.exp 2009-08-11 03:11:26.000000000 +1000
+++ tc06_two_races_xml.stderr.out 2009-08-11 03:19:04.000000000 +1000
@@ -44,16 +44,6 @@
<frame>
<ip>0x........</ip>
<obj>...</obj>
- <fn>do_clone</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>pthread_create@@GLIBC_2.2.5</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<fn>pthread_create_WRK</fn>
<dir>...</dir>
<file>hg_intercepts.c</file>
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2009-08-11 03:11:47.000000000 +1000
+++ origin5-bz2.stderr.out 2009-08-11 03:16:33.000000000 +1000
@@ -11,7 +11,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -19,7 +19,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -27,7 +27,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -38,7 +38,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -49,7 +49,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2854)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -60,7 +60,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2858)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -71,7 +71,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -82,7 +82,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -93,7 +93,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -104,7 +104,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2275)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2009-08-11 03:11:47.000000000 +1000
+++ origin5-bz2.stderr.out 2009-08-11 03:16:33.000000000 +1000
@@ -28,7 +28,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -38,7 +39,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -48,7 +50,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2855)
+ at 0x........: mainSort (origin5-bz2.c:2854)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -58,7 +61,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2859)
+ at 0x........: mainSort (origin5-bz2.c:2858)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -68,7 +72,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -78,7 +83,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2964)
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2009-08-11 03:11:47.000000000 +1000
+++ origin5-bz2.stderr.out 2009-08-11 03:16:33.000000000 +1000
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: handle_compress (origin5-bz2.c:4686)
@@ -9,85 +9,91 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2854)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2858)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
<truncated beyond 100 lines>
=================================================
./valgrind-new/none/tests/empty-exe.stderr.diff
=================================================
--- empty-exe.stderr.exp 2009-08-11 03:12:11.000000000 +1000
+++ empty-exe.stderr.out 2009-08-11 03:17:59.000000000 +1000
@@ -1,2 +1,2 @@
-
-
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./empty-exe: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell.stderr.diff
=================================================
--- shell.stderr.exp 2009-08-11 03:12:11.000000000 +1000
+++ shell.stderr.out 2009-08-11 03:18:19.000000000 +1000
@@ -1,8 +1,3 @@
-./shell: ./x86/: is a directory
-./shell: ./shell.vgtest: Permission denied
-execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2
-EXEC FAILED: I can't recover from execve() failing, so I'm dying.
-Add more stringent tests in PRE(sys_execve), or work out how to recover.
-./shell: ./shell_binaryfile: cannot execute binary file
-./shell: ./shell_nosuchfile: No such file or directory
-./shell: shell_nosuchfile: command not found
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell.stderr.diff-dash
=================================================
--- shell.stderr.exp-dash 2009-08-11 03:12:11.000000000 +1000
+++ shell.stderr.out 2009-08-11 03:18:19.000000000 +1000
@@ -1,8 +1,3 @@
-./shell: 10: ./x86/: Permission denied
-./shell: 13: ./shell.vgtest: Permission denied
-execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2
-EXEC FAILED: I can't recover from execve() failing, so I'm dying.
-Add more stringent tests in PRE(sys_execve), or work out how to recover.
-./shell_binaryfile: 4: Syntax error: ")" unexpected
-./shell: 22: ./shell_nosuchfile: not found
-./shell: 25: shell_nosuchfile: not found
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell.stdout.diff
=================================================
--- shell.stdout.exp 2009-08-11 03:12:11.000000000 +1000
+++ shell.stdout.out 2009-08-11 03:18:19.000000000 +1000
@@ -1,10 +0,0 @@
-Execute a directory
-Execute a non-executable file
-Execute a script with a bad interpreter name
-Execute a binary file
-Execute a non-existent file
-Execute a non-existent file (2)
-Execute a valid script with a #! line
-Execute a valid script without a #! line
-Execute a valid script with #! but no interpname
-Execute a zero-length file
=================================================
./valgrind-new/none/tests/shell_valid1.stderr.diff
=================================================
--- shell_valid1.stderr.exp 2009-08-11 03:12:11.000000000 +1000
+++ shell_valid1.stderr.out 2009-08-11 03:18:19.000000000 +1000
@@ -0,0 +1,3 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid1: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell_valid2.stderr.diff
=================================================
--- shell_valid2.stderr.exp 2009-08-11 03:12:11.000000000 +1000
+++ shell_valid2.stderr.out 2009-08-11 03:18:20.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid2: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell_valid3.stderr.diff
=================================================
--- shell_valid3.stderr.exp 2009-08-11 03:12:11.000000000 +1000
+++ shell_valid3.stderr.out 2009-08-11 03:18:20.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid3: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell_zerolength.stderr.diff
=================================================
--- shell_zerolength.stderr.exp 2009-08-11 03:12:11.000000000 +1000
+++ shell_zerolength.stderr.out 2009-08-11 03:18:20.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_zerolength: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-new/none/tests/shell_zerolength.stderr.diff-dash
=================================================
--- shell_zerolength.stderr.exp-dash 2009-08-11 03:12:11.000000000 +1000
+++ shell_zerolength.stderr.out 2009-08-11 03:18:20.000000000 +1000
@@ -1 +1,2 @@
-Bus error
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_zerolength: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/exp-ptrcheck/tests/supp.stderr.diff
=================================================
--- supp.stderr.exp 2009-08-11 03:00:41.000000000 +1000
+++ supp.stderr.out 2009-08-11 03:11:06.000000000 +1000
@@ -1,7 +1,7 @@
Syscall param write(buf) is non-contiguous
- at 0x........: write (in /...libc...)
- by 0x........: main (supp.c:16)
+ at 0x........: ??? (in /lib32/ld-2.9.so)
+ by 0x........: (below main)
First byte (0x........) is 3 bytes inside a 6-byte block alloc'd
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: main (supp.c:12)
=================================================
./valgrind-old/helgrind/tests/tc06_two_races_xml.stderr.diff
=================================================
--- tc06_two_races_xml.stderr.exp 2009-08-11 03:00:37.000000000 +1000
+++ tc06_two_races_xml.stderr.out 2009-08-11 03:08:32.000000000 +1000
@@ -44,16 +44,6 @@
<frame>
<ip>0x........</ip>
<obj>...</obj>
- <fn>do_clone</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>pthread_create@@GLIBC_2.2.5</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<fn>pthread_create_WRK</fn>
<dir>...</dir>
<file>hg_intercepts.c</file>
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2009-08-11 03:01:07.000000000 +1000
+++ origin5-bz2.stderr.out 2009-08-11 03:05:59.000000000 +1000
@@ -11,7 +11,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -19,7 +19,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -27,7 +27,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -38,7 +38,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -49,7 +49,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2854)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -60,7 +60,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2858)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -71,7 +71,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -82,7 +82,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -93,7 +93,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -104,7 +104,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2275)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2009-08-11 03:01:07.000000000 +1000
+++ origin5-bz2.stderr.out 2009-08-11 03:05:59.000000000 +1000
@@ -28,7 +28,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -38,7 +39,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -48,7 +50,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2855)
+ at 0x........: mainSort (origin5-bz2.c:2854)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -58,7 +61,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2859)
+ at 0x........: mainSort (origin5-bz2.c:2858)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -68,7 +72,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -78,7 +83,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2964)
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2009-08-11 03:01:07.000000000 +1000
+++ origin5-bz2.stderr.out 2009-08-11 03:05:59.000000000 +1000
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: handle_compress (origin5-bz2.c:4686)
@@ -9,85 +9,91 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2854)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2858)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
<truncated beyond 100 lines>
=================================================
./valgrind-old/none/tests/empty-exe.stderr.diff
=================================================
--- empty-exe.stderr.exp 2009-08-11 03:01:38.000000000 +1000
+++ empty-exe.stderr.out 2009-08-11 03:07:27.000000000 +1000
@@ -1,2 +1,2 @@
-
-
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./empty-exe: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell.stderr.diff
=================================================
--- shell.stderr.exp 2009-08-11 03:01:38.000000000 +1000
+++ shell.stderr.out 2009-08-11 03:07:48.000000000 +1000
@@ -1,8 +1,3 @@
-./shell: ./x86/: is a directory
-./shell: ./shell.vgtest: Permission denied
-execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2
-EXEC FAILED: I can't recover from execve() failing, so I'm dying.
-Add more stringent tests in PRE(sys_execve), or work out how to recover.
-./shell: ./shell_binaryfile: cannot execute binary file
-./shell: ./shell_nosuchfile: No such file or directory
-./shell: shell_nosuchfile: command not found
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell.stderr.diff-dash
=================================================
--- shell.stderr.exp-dash 2009-08-11 03:01:38.000000000 +1000
+++ shell.stderr.out 2009-08-11 03:07:48.000000000 +1000
@@ -1,8 +1,3 @@
-./shell: 10: ./x86/: Permission denied
-./shell: 13: ./shell.vgtest: Permission denied
-execve(0x........(./shell_badinterp), 0x........, 0x........) failed, errno 2
-EXEC FAILED: I can't recover from execve() failing, so I'm dying.
-Add more stringent tests in PRE(sys_execve), or work out how to recover.
-./shell_binaryfile: 4: Syntax error: ")" unexpected
-./shell: 22: ./shell_nosuchfile: not found
-./shell: 25: shell_nosuchfile: not found
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell.stdout.diff
=================================================
--- shell.stdout.exp 2009-08-11 03:01:38.000000000 +1000
+++ shell.stdout.out 2009-08-11 03:07:48.000000000 +1000
@@ -1,10 +0,0 @@
-Execute a directory
-Execute a non-executable file
-Execute a script with a bad interpreter name
-Execute a binary file
-Execute a non-existent file
-Execute a non-existent file (2)
-Execute a valid script with a #! line
-Execute a valid script without a #! line
-Execute a valid script with #! but no interpname
-Execute a zero-length file
=================================================
./valgrind-old/none/tests/shell_valid1.stderr.diff
=================================================
--- shell_valid1.stderr.exp 2009-08-11 03:01:38.000000000 +1000
+++ shell_valid1.stderr.out 2009-08-11 03:07:48.000000000 +1000
@@ -0,0 +1,3 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid1: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell_valid2.stderr.diff
=================================================
--- shell_valid2.stderr.exp 2009-08-11 03:01:38.000000000 +1000
+++ shell_valid2.stderr.out 2009-08-11 03:07:48.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid2: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell_valid3.stderr.diff
=================================================
--- shell_valid3.stderr.exp 2009-08-11 03:01:38.000000000 +1000
+++ shell_valid3.stderr.out 2009-08-11 03:07:48.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_valid3: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell_zerolength.stderr.diff
=================================================
--- shell_zerolength.stderr.exp 2009-08-11 03:01:38.000000000 +1000
+++ shell_zerolength.stderr.out 2009-08-11 03:07:48.000000000 +1000
@@ -0,0 +1,2 @@
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_zerolength: bad interpreter (/bin/sh): VG_(strerror): unknown error
=================================================
./valgrind-old/none/tests/shell_zerolength.stderr.diff-dash
=================================================
--- shell_zerolength.stderr.exp-dash 2009-08-11 03:01:38.000000000 +1000
+++ shell_zerolength.stderr.out 2009-08-11 03:07:48.000000000 +1000
@@ -1 +1,2 @@
-Bus error
+valgrind: wrong ELF executable class (eg. 32-bit instead of 64-bit)
+valgrind: ./shell_zerolength: bad interpreter (/bin/sh): VG_(strerror): unknown error
|
|
From: Nicholas N. <n.n...@gm...> - 2009-08-10 16:26:47
|
Nightly build on ocean ( Ubuntu 9.04, x86_64 )
Started at 2009-08-11 02:00:01 EST
Ended at 2009-08-11 02:26:28 EST
Results differ from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 527 tests, 1 stderr failure, 0 stdout failures, 0 post failures ==
helgrind/tests/tc06_two_races_xml (stderr)
=================================================
== Results from 24 hours ago ==
=================================================
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 526 tests, 1 stderr failure, 0 stdout failures, 0 post failures ==
helgrind/tests/tc06_two_races_xml (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Tue Aug 11 02:12:25 2009
--- new.short Tue Aug 11 02:26:28 2009
***************
*** 8,10 ****
! == 526 tests, 1 stderr failure, 0 stdout failures, 0 post failures ==
helgrind/tests/tc06_two_races_xml (stderr)
--- 8,10 ----
! == 527 tests, 1 stderr failure, 0 stdout failures, 0 post failures ==
helgrind/tests/tc06_two_races_xml (stderr)
=================================================
./valgrind-new/helgrind/tests/tc06_two_races_xml.stderr.diff
=================================================
--- tc06_two_races_xml.stderr.exp 2009-08-11 02:12:46.000000000 +1000
+++ tc06_two_races_xml.stderr.out 2009-08-11 02:24:10.000000000 +1000
@@ -44,11 +44,6 @@
<frame>
<ip>0x........</ip>
<obj>...</obj>
- <fn>do_clone</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<fn>pthread_create@@GLIBC_2.2.5</fn>
</frame>
<frame>
=================================================
./valgrind-old/helgrind/tests/tc06_two_races_xml.stderr.diff
=================================================
--- tc06_two_races_xml.stderr.exp 2009-08-11 02:00:35.000000000 +1000
+++ tc06_two_races_xml.stderr.out 2009-08-11 02:10:07.000000000 +1000
@@ -44,11 +44,6 @@
<frame>
<ip>0x........</ip>
<obj>...</obj>
- <fn>do_clone</fn>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<fn>pthread_create@@GLIBC_2.2.5</fn>
</frame>
<frame>
|
|
From: <sv...@va...> - 2009-08-10 14:13:24
|
Author: bart
Date: 2009-08-10 15:13:12 +0100 (Mon, 10 Aug 2009)
New Revision: 10769
Log:
Added suppression patterns for the most recent libglib and libQtCore versions.
Modified:
trunk/glibc-2.X-drd.supp
Modified: trunk/glibc-2.X-drd.supp
===================================================================
--- trunk/glibc-2.X-drd.supp 2009-08-10 08:25:39 UTC (rev 10768)
+++ trunk/glibc-2.X-drd.supp 2009-08-10 14:13:12 UTC (rev 10769)
@@ -166,6 +166,13 @@
drd:ConflictingAccess
fun:g_slice_free_chain_with_offset
}
+{
+ drd-libglib-g_main_context_new
+ drd:ConflictingAccess
+ fun:fcntl
+ obj:/usr/lib*/libglib-*.so*
+ fun:g_main_context_new
+}
#
# Suppression patterns for libQtCore.
@@ -203,6 +210,11 @@
fun:_ZN24QAbstractEventDispatcherD2Ev
fun:_ZN20QEventDispatcherGlibD0Ev
}
+{
+ drd-libQtCore-QMutexPool::get(void const*)
+ drd:ConflictingAccess
+ fun:_ZN10QMutexPool3getEPKv
+}
#
# Suppression patterns for libboost.
|
|
From: Julian S. <js...@ac...> - 2009-08-10 14:03:48
|
On Monday 10 August 2009, sv...@va... wrote: > Author: njn > Date: 2009-08-10 08:50:00 +0100 (Mon, 10 Aug 2009) > New Revision: 10767 > > Log: > Count leak as errors. Fixes bug 152393. But then we get this: ==29908== ERROR SUMMARY: 71 errors from 0 contexts (suppressed: 111 from 2) which is confusing. I'm wondering if there's a different way to fix 152393, perhaps by adding a --warning-exitcode= flag. Problem is the core has no notion of major vs minor errors. Hmm. J |
|
From: Rich C. <Ric...@me...> - 2009-08-10 12:52:48
|
Nightly build on macbook ( Darwin 9.8.0 i386 )
Started at 2009-08-09 23:05:00 CDT
Ended at 2009-08-09 23:29:31 CDT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 378 tests, 6 stderr failures, 1 stdout failure, 0 post failures ==
memcheck/tests/null_socket (stdout)
memcheck/tests/origin5-bz2 (stderr)
memcheck/tests/varinfo3 (stderr)
memcheck/tests/varinfo5 (stderr)
none/tests/async-sigs (stderr)
none/tests/faultstatus (stderr)
none/tests/pth_blockedsig (stderr)
=================================================
./valgrind-new/memcheck/tests/null_socket.stdout.diff
=================================================
--- /dev/null 2009-08-09 23:23:08.000000000 -0500
+++ null_socket.stdout.out 2009-08-09 23:23:25.000000000 -0500
@@ -0,0 +1 @@
+recvfrom succeeded?
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2009-08-09 23:17:45.000000000 -0500
+++ origin5-bz2.stderr.out 2009-08-09 23:23:40.000000000 -0500
@@ -11,7 +11,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -19,7 +19,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -27,7 +27,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -38,7 +38,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -49,8 +49,8 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2855)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
@@ -60,8 +60,8 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2859)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
@@ -71,7 +71,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -82,7 +82,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -93,7 +93,18 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
+ by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
+ by 0x........: handle_compress (origin5-bz2.c:4753)
+ by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
+ by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
+ by 0x........: main (origin5-bz2.c:6484)
+ Uninitialised value was created by a client request
+ at 0x........: main (origin5-bz2.c:6479)
+
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -104,7 +115,7 @@
Uninitialised value was created by a client request
<truncated beyond 100 lines>
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2009-08-09 23:17:46.000000000 -0500
+++ origin5-bz2.stderr.out 2009-08-09 23:23:40.000000000 -0500
@@ -28,7 +28,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -38,7 +39,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -48,7 +50,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2855)
+ at 0x........: mainSort (origin5-bz2.c:2855)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -58,7 +61,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2859)
+ at 0x........: mainSort (origin5-bz2.c:2859)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -68,7 +72,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -78,7 +83,19 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2964)
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
+ by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
+ by 0x........: handle_compress (origin5-bz2.c:4753)
+ by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
+ by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
+ by 0x........: main (origin5-bz2.c:6484)
+ Uninitialised value was created by a client request
+ at 0x........: main (origin5-bz2.c:6479)
+
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
=================================================
./valgrind-new/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2009-08-09 23:17:45.000000000 -0500
+++ origin5-bz2.stderr.out 2009-08-09 23:23:40.000000000 -0500
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: handle_compress (origin5-bz2.c:4686)
@@ -9,85 +9,102 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2855)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2859)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
<truncated beyond 100 lines>
=================================================
./valgrind-new/memcheck/tests/varinfo3.stderr.diff
=================================================
--- varinfo3.stderr.exp 2009-08-09 23:17:45.000000000 -0500
+++ varinfo3.stderr.out 2009-08-09 23:24:35.000000000 -0500
@@ -31,7 +31,7 @@
by 0x........: bar (varinfo3.c:42)
by 0x........: foo (varinfo3.c:58)
by 0x........: main (varinfo3.c:66)
- Address 0x........ is 5 bytes inside data symbol "static_local_def.XXXX"
+ Address 0x........ is in the Data segment of ./varinfo3
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo3.c:28)
@@ -46,7 +46,7 @@
by 0x........: bar (varinfo3.c:44)
by 0x........: foo (varinfo3.c:58)
by 0x........: main (varinfo3.c:66)
- Address 0x........ is 7 bytes inside data symbol "static_local_undef.XXXX"
+ Address 0x........ is in the Data segment of ./varinfo3
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo3.c:28)
=================================================
./valgrind-new/memcheck/tests/varinfo5.stderr.diff
=================================================
--- varinfo5.stderr.exp 2009-08-09 23:17:46.000000000 -0500
+++ varinfo5.stderr.out 2009-08-09 23:24:37.000000000 -0500
@@ -119,7 +119,7 @@
by 0x........: varinfo3_main (varinfo5so.c:118)
by 0x........: varinfo5_main (varinfo5so.c:156)
by 0x........: main (varinfo5.c:5)
- Address 0x........ is 5 bytes inside data symbol "static_local_def.XXXX"
+ Address 0x........ is in the Data segment of /Users/minime/src/vg/nightly/valgrind-new/memcheck/tests/varinfo5so.so
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo5so.c:29)
@@ -138,7 +138,7 @@
by 0x........: varinfo3_main (varinfo5so.c:118)
by 0x........: varinfo5_main (varinfo5so.c:156)
by 0x........: main (varinfo5.c:5)
- Address 0x........ is 7 bytes inside data symbol "static_local_undef.XXXX"
+ Address 0x........ is in the Data segment of /Users/minime/src/vg/nightly/valgrind-new/memcheck/tests/varinfo5so.so
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo5so.c:29)
=================================================
./valgrind-new/none/tests/async-sigs.stderr.diff
=================================================
--- async-sigs.stderr.exp 2009-08-09 23:17:54.000000000 -0500
+++ async-sigs.stderr.out 2009-08-09 23:26:02.000000000 -0500
@@ -1,8 +1,30 @@
-testing: blocking=0 caught=11 fatal=7... PASSED
+testing: blocking=0 caught=11 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: test (async-sigs.c:94)
+ by 0x........: main (async-sigs.c:129)
+PASSED
testing: blocking=0 caught=11 fatal=1... PASSED
-testing: blocking=0 caught=10 fatal=7... PASSED
-testing: blocking=0 caught=10 fatal=1... PASSED
-testing: blocking=1 caught=11 fatal=7... PASSED
+testing: blocking=0 caught=30 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: test (async-sigs.c:94)
+ by 0x........: main (async-sigs.c:131)
+PASSED
+testing: blocking=0 caught=30 fatal=1... PASSED
+testing: blocking=1 caught=11 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: __sigsuspend (in /...libc...)
+ by 0x........: test (async-sigs.c:95)
+ by 0x........: main (async-sigs.c:133)
+PASSED
testing: blocking=1 caught=11 fatal=1... PASSED
-testing: blocking=1 caught=10 fatal=7... PASSED
-testing: blocking=1 caught=10 fatal=1... PASSED
+testing: blocking=1 caught=30 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: __sigsuspend (in /...libc...)
+ by 0x........: test (async-sigs.c:95)
+ by 0x........: main (async-sigs.c:135)
+PASSED
+testing: blocking=1 caught=30 fatal=1... PASSED
=================================================
./valgrind-new/none/tests/faultstatus.stderr.diff
=================================================
--- faultstatus.stderr.exp 2009-08-09 23:17:55.000000000 -0500
+++ faultstatus.stderr.out 2009-08-09 23:26:07.000000000 -0500
@@ -1,6 +1,6 @@
-Test 1: PASS
-Test 2: PASS
-Test 3: PASS
-Test 4: PASS
+Test 1: FAIL: expected signal 11, not 10
+Test 2: FAIL: expected signal 11, not 10
+Test 3: FAIL: no fault, or handler returned
+Test 4: FAIL: expected si_code==7, not 0
=================================================
./valgrind-new/none/tests/pth_blockedsig.stderr.diff
=================================================
--- pth_blockedsig.stderr.exp 2009-08-09 23:17:54.000000000 -0500
+++ pth_blockedsig.stderr.out 2009-08-09 23:27:08.000000000 -0500
@@ -1,2 +1,4 @@
+UNKNOWN __pthread_sigmask is unsupported. This warning will not be repeated.
+SHOULD NOT BE HERE (SIGUSR1)!!!!
=================================================
./valgrind-old/memcheck/tests/null_socket.stdout.diff
=================================================
--- /dev/null 2009-08-09 23:11:12.000000000 -0500
+++ null_socket.stdout.out 2009-08-09 23:11:29.000000000 -0500
@@ -0,0 +1 @@
+recvfrom succeeded?
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-amd64
=================================================
--- origin5-bz2.stderr.exp-glibc25-amd64 2009-08-09 23:05:33.000000000 -0500
+++ origin5-bz2.stderr.out 2009-08-09 23:11:44.000000000 -0500
@@ -11,7 +11,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -19,7 +19,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
@@ -27,7 +27,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2820)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -38,7 +38,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2823)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -49,8 +49,8 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2855)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
@@ -60,8 +60,8 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: mainSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2859)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
@@ -71,7 +71,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2963)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -82,7 +82,7 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: mainSort (origin5-bz2.c:2964)
by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -93,7 +93,18 @@
Uninitialised value was created by a client request
at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
+ by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
+ by 0x........: handle_compress (origin5-bz2.c:4753)
+ by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
+ by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
+ by 0x........: main (origin5-bz2.c:6484)
+ Uninitialised value was created by a client request
+ at 0x........: main (origin5-bz2.c:6479)
+
+Use of uninitialised value of size 4
at 0x........: fallbackSort (origin5-bz2.c:2269)
by 0x........: BZ2_blockSort (origin5-bz2.c:3116)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
@@ -104,7 +115,7 @@
Uninitialised value was created by a client request
<truncated beyond 100 lines>
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc25-x86
=================================================
--- origin5-bz2.stderr.exp-glibc25-x86 2009-08-09 23:05:34.000000000 -0500
+++ origin5-bz2.stderr.out 2009-08-09 23:11:44.000000000 -0500
@@ -28,7 +28,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -38,7 +39,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -48,7 +50,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2855)
+ at 0x........: mainSort (origin5-bz2.c:2855)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -58,7 +61,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2859)
+ at 0x........: mainSort (origin5-bz2.c:2859)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -68,7 +72,8 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
@@ -78,7 +83,19 @@
at 0x........: main (origin5-bz2.c:6479)
Use of uninitialised value of size 4
- at 0x........: BZ2_blockSort (origin5-bz2.c:2964)
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
+ by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
+ by 0x........: handle_compress (origin5-bz2.c:4753)
+ by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
+ by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
+ by 0x........: main (origin5-bz2.c:6484)
+ Uninitialised value was created by a client request
+ at 0x........: main (origin5-bz2.c:6479)
+
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2964)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
=================================================
./valgrind-old/memcheck/tests/origin5-bz2.stderr.diff-glibc27-ppc64
=================================================
--- origin5-bz2.stderr.exp-glibc27-ppc64 2009-08-09 23:05:33.000000000 -0500
+++ origin5-bz2.stderr.out 2009-08-09 23:11:44.000000000 -0500
@@ -1,7 +1,7 @@
Conditional jump or move depends on uninitialised value(s)
at 0x........: main (origin5-bz2.c:6481)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
Conditional jump or move depends on uninitialised value(s)
at 0x........: handle_compress (origin5-bz2.c:4686)
@@ -9,85 +9,102 @@
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
+Use of uninitialised value of size 4
at 0x........: handle_compress (origin5-bz2.c:4686)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2820)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2820)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2823)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2823)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2854)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2855)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2858)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2859)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
by 0x........: handle_compress (origin5-bz2.c:4753)
by 0x........: BZ2_bzCompress (origin5-bz2.c:4822)
by 0x........: BZ2_bzBuffToBuffCompress (origin5-bz2.c:5630)
by 0x........: main (origin5-bz2.c:6484)
Uninitialised value was created by a client request
- at 0x........: main (origin5-bz2.c:6481)
+ at 0x........: main (origin5-bz2.c:6479)
-Use of uninitialised value of size 8
- at 0x........: BZ2_blockSort (origin5-bz2.c:2963)
+Use of uninitialised value of size 4
+ at 0x........: mainSort (origin5-bz2.c:2963)
+ by 0x........: BZ2_blockSort (origin5-bz2.c:3105)
by 0x........: BZ2_compressBlock (origin5-bz2.c:4034)
<truncated beyond 100 lines>
=================================================
./valgrind-old/memcheck/tests/varinfo3.stderr.diff
=================================================
--- varinfo3.stderr.exp 2009-08-09 23:05:33.000000000 -0500
+++ varinfo3.stderr.out 2009-08-09 23:12:39.000000000 -0500
@@ -31,7 +31,7 @@
by 0x........: bar (varinfo3.c:42)
by 0x........: foo (varinfo3.c:58)
by 0x........: main (varinfo3.c:66)
- Address 0x........ is 5 bytes inside data symbol "static_local_def.XXXX"
+ Address 0x........ is in the Data segment of ./varinfo3
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo3.c:28)
@@ -46,7 +46,7 @@
by 0x........: bar (varinfo3.c:44)
by 0x........: foo (varinfo3.c:58)
by 0x........: main (varinfo3.c:66)
- Address 0x........ is 7 bytes inside data symbol "static_local_undef.XXXX"
+ Address 0x........ is in the Data segment of ./varinfo3
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo3.c:28)
=================================================
./valgrind-old/memcheck/tests/varinfo5.stderr.diff
=================================================
--- varinfo5.stderr.exp 2009-08-09 23:05:33.000000000 -0500
+++ varinfo5.stderr.out 2009-08-09 23:12:41.000000000 -0500
@@ -119,7 +119,7 @@
by 0x........: varinfo3_main (varinfo5so.c:118)
by 0x........: varinfo5_main (varinfo5so.c:156)
by 0x........: main (varinfo5.c:5)
- Address 0x........ is 5 bytes inside data symbol "static_local_def.XXXX"
+ Address 0x........ is in the Data segment of /Users/minime/src/vg/nightly/valgrind-old/memcheck/tests/varinfo5so.so
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo5so.c:29)
@@ -138,7 +138,7 @@
by 0x........: varinfo3_main (varinfo5so.c:118)
by 0x........: varinfo5_main (varinfo5so.c:156)
by 0x........: main (varinfo5.c:5)
- Address 0x........ is 7 bytes inside data symbol "static_local_undef.XXXX"
+ Address 0x........ is in the Data segment of /Users/minime/src/vg/nightly/valgrind-old/memcheck/tests/varinfo5so.so
Uninitialised byte(s) found during client check request
at 0x........: croak (varinfo5so.c:29)
=================================================
./valgrind-old/none/tests/async-sigs.stderr.diff
=================================================
--- async-sigs.stderr.exp 2009-08-09 23:05:49.000000000 -0500
+++ async-sigs.stderr.out 2009-08-09 23:14:06.000000000 -0500
@@ -1,8 +1,30 @@
-testing: blocking=0 caught=11 fatal=7... PASSED
+testing: blocking=0 caught=11 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: test (async-sigs.c:94)
+ by 0x........: main (async-sigs.c:129)
+PASSED
testing: blocking=0 caught=11 fatal=1... PASSED
-testing: blocking=0 caught=10 fatal=7... PASSED
-testing: blocking=0 caught=10 fatal=1... PASSED
-testing: blocking=1 caught=11 fatal=7... PASSED
+testing: blocking=0 caught=30 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: test (async-sigs.c:94)
+ by 0x........: main (async-sigs.c:131)
+PASSED
+testing: blocking=0 caught=30 fatal=1... PASSED
+testing: blocking=1 caught=11 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: __sigsuspend (in /...libc...)
+ by 0x........: test (async-sigs.c:95)
+ by 0x........: main (async-sigs.c:133)
+PASSED
testing: blocking=1 caught=11 fatal=1... PASSED
-testing: blocking=1 caught=10 fatal=7... PASSED
-testing: blocking=1 caught=10 fatal=1... PASSED
+testing: blocking=1 caught=30 fatal=10...
+Process terminating with default action of signal 10 (SIGBUS)
+ Non-existent physical address at address 0x........
+ at 0x........: __sigsuspend (in /...libc...)
+ by 0x........: test (async-sigs.c:95)
+ by 0x........: main (async-sigs.c:135)
+PASSED
+testing: blocking=1 caught=30 fatal=1... PASSED
=================================================
./valgrind-old/none/tests/faultstatus.stderr.diff
=================================================
--- faultstatus.stderr.exp 2009-08-09 23:05:49.000000000 -0500
+++ faultstatus.stderr.out 2009-08-09 23:14:11.000000000 -0500
@@ -1,6 +1,6 @@
-Test 1: PASS
-Test 2: PASS
-Test 3: PASS
-Test 4: PASS
+Test 1: FAIL: expected signal 11, not 10
+Test 2: FAIL: expected signal 11, not 10
+Test 3: FAIL: no fault, or handler returned
+Test 4: FAIL: expected si_code==7, not 0
=================================================
./valgrind-old/none/tests/pth_blockedsig.stderr.diff
=================================================
--- pth_blockedsig.stderr.exp 2009-08-09 23:05:49.000000000 -0500
+++ pth_blockedsig.stderr.out 2009-08-09 23:15:11.000000000 -0500
@@ -1,2 +1,4 @@
+UNKNOWN __pthread_sigmask is unsupported. This warning will not be repeated.
+SHOULD NOT BE HERE (SIGUSR1)!!!!
|
|
From: <sv...@va...> - 2009-08-10 08:25:50
|
Author: njn
Date: 2009-08-10 09:25:39 +0100 (Mon, 10 Aug 2009)
New Revision: 10768
Log:
Try to fix error_counts.
Removed:
trunk/memcheck/tests/error_counts.stdout.exp
Modified:
trunk/coregrind/m_errormgr.c
trunk/include/pub_tool_errormgr.h
trunk/memcheck/mc_errors.c
trunk/memcheck/mc_include.h
trunk/memcheck/mc_leakcheck.c
trunk/memcheck/tests/Makefile.am
trunk/memcheck/tests/error_counts.c
trunk/memcheck/tests/error_counts.stderr.exp
Modified: trunk/coregrind/m_errormgr.c
===================================================================
--- trunk/coregrind/m_errormgr.c 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/coregrind/m_errormgr.c 2009-08-10 08:25:39 UTC (rev 10768)
@@ -737,10 +737,11 @@
guaranteed to only happen once. This avoids all the recording and
comparing stuff. But they can be suppressed; returns True if it is
suppressed. Bool 'print_error' dictates whether to print the error.
+ Bool 'count_error' dictates whether to count the error in n_errs_found.
*/
Bool VG_(unique_error) ( ThreadId tid, ErrorKind ekind, Addr a, Char* s,
void* extra, ExeContext* where, Bool print_error,
- Bool allow_db_attach )
+ Bool allow_db_attach, Bool count_error )
{
Error err;
Supp *su;
@@ -759,7 +760,8 @@
su = is_suppressible_error(&err);
if (NULL == su) {
- n_errs_found++;
+ if (count_error)
+ n_errs_found++;
if (print_error) {
/* A bit of prettyprinting, to ensure there's a blank line
Modified: trunk/include/pub_tool_errormgr.h
===================================================================
--- trunk/include/pub_tool_errormgr.h 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/include/pub_tool_errormgr.h 2009-08-10 08:25:39 UTC (rev 10768)
@@ -85,7 +85,7 @@
extern Bool VG_(unique_error) ( ThreadId tid, ErrorKind ekind,
Addr a, Char* s, void* extra,
ExeContext* where, Bool print_error,
- Bool allow_GDB_attach );
+ Bool allow_GDB_attach, Bool count_error );
/* Gets a non-blank, non-comment line from fd. bufpp is a pointer to a
pointer to a buffer that must be allocated with VG_(malloc); nBufp is a
Modified: trunk/memcheck/mc_errors.c
===================================================================
--- trunk/memcheck/mc_errors.c 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/memcheck/mc_errors.c 2009-08-10 08:25:39 UTC (rev 10768)
@@ -942,7 +942,7 @@
Bool MC_(record_leak_error) ( ThreadId tid, UInt n_this_record,
UInt n_total_records, LossRecord* lr,
- Bool print_record )
+ Bool print_record, Bool count_error )
{
MC_Error extra;
extra.Err.Leak.n_this_record = n_this_record;
@@ -951,7 +951,7 @@
return
VG_(unique_error) ( tid, Err_Leak, /*Addr*/0, /*s*/NULL, &extra,
lr->key.allocated_at, print_record,
- /*allow_GDB_attach*/False );
+ /*allow_GDB_attach*/False, count_error );
}
void MC_(record_user_error) ( ThreadId tid, Addr a,
Modified: trunk/memcheck/mc_include.h
===================================================================
--- trunk/memcheck/mc_include.h 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/memcheck/mc_include.h 2009-08-10 08:25:39 UTC (rev 10768)
@@ -348,7 +348,8 @@
UInt n_this_record,
UInt n_total_records,
LossRecord* lossRecord,
- Bool print_record );
+ Bool print_record,
+ Bool count_error );
/* Is this address in a user-specified "ignored range" ? */
Bool MC_(in_ignored_range) ( Addr a );
Modified: trunk/memcheck/mc_leakcheck.c
===================================================================
--- trunk/memcheck/mc_leakcheck.c 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/memcheck/mc_leakcheck.c 2009-08-10 08:25:39 UTC (rev 10768)
@@ -828,7 +828,7 @@
// Print the loss records (in size order) and collect summary stats.
for (i = 0; i < n_lossrecords; i++) {
- Bool print_record;
+ Bool count_as_error, print_record;
// Rules for printing:
// - We don't show suppressed loss records ever (and that's controlled
// within the error manager).
@@ -842,12 +842,13 @@
// includes indirectly lost blocks!
//
lr = lr_array[i];
+ count_as_error = Unreached == lr->key.state ||
+ Possible == lr->key.state;
print_record = is_full_check &&
- ( MC_(clo_show_reachable) ||
- Unreached == lr->key.state ||
- Possible == lr->key.state );
+ ( MC_(clo_show_reachable) || count_as_error );
is_suppressed =
- MC_(record_leak_error) ( tid, i+1, n_lossrecords, lr, print_record );
+ MC_(record_leak_error) ( tid, i+1, n_lossrecords, lr, print_record,
+ count_as_error );
if (is_suppressed) {
MC_(blocks_suppressed) += lr->num_blocks;
Modified: trunk/memcheck/tests/Makefile.am
===================================================================
--- trunk/memcheck/tests/Makefile.am 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/memcheck/tests/Makefile.am 2009-08-10 08:25:39 UTC (rev 10768)
@@ -59,7 +59,7 @@
describe-block.stderr.exp describe-block.vgtest \
doublefree.stderr.exp doublefree.vgtest \
erringfds.stderr.exp erringfds.stdout.exp erringfds.vgtest \
- error_counts.stderr.exp error_counts.stdout.exp error_counts.vgtest \
+ error_counts.stderr.exp error_counts.vgtest \
errs1.stderr.exp errs1.vgtest \
exitprog.stderr.exp exitprog.vgtest \
execve.stderr.exp execve.vgtest \
Modified: trunk/memcheck/tests/error_counts.c
===================================================================
--- trunk/memcheck/tests/error_counts.c 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/memcheck/tests/error_counts.c 2009-08-10 08:25:39 UTC (rev 10768)
@@ -17,7 +17,7 @@
assert(sizeof(long) == sizeof(void*));
/* Error counting */
- printf("errors: %d\n\n", VALGRIND_COUNT_ERRORS);
+ fprintf(stderr, "errors: %d\n\n", VALGRIND_COUNT_ERRORS);
if (x == 0) {
y++;
@@ -25,17 +25,21 @@
y--;
}
- printf("errors: %d\n\n", VALGRIND_COUNT_ERRORS);
+ fprintf(stderr, "errors: %d\n\n", VALGRIND_COUNT_ERRORS);
// Get a baseline, after start-up and also after printf (because Darwin
// printf allocates memory the first time it's called!)
GET_INITIAL_LEAK_COUNTS;
+ fprintf(stderr, "errors: %d\n\n", VALGRIND_COUNT_ERRORS);
+
/* Leak checking */
GET_FINAL_LEAK_COUNTS;
- PRINT_LEAK_COUNTS(stdout);
- printf("\n");
+ PRINT_LEAK_COUNTS(stderr);
+ fprintf(stderr, "\n");
+ fprintf(stderr, "errors: %d\n\n", VALGRIND_COUNT_ERRORS);
+
leaked = malloc(77);
leaked = 0;
@@ -45,10 +49,10 @@
reachable = malloc(99);
GET_FINAL_LEAK_COUNTS;
- PRINT_LEAK_COUNTS(stdout);
- printf("\n");
+ PRINT_LEAK_COUNTS(stderr);
+ fprintf(stderr, "\n");
- printf("errors: %d\n", VALGRIND_COUNT_ERRORS);
+ fprintf(stderr, "errors: %d\n", VALGRIND_COUNT_ERRORS);
return 0;
}
Modified: trunk/memcheck/tests/error_counts.stderr.exp
===================================================================
--- trunk/memcheck/tests/error_counts.stderr.exp 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/memcheck/tests/error_counts.stderr.exp 2009-08-10 08:25:39 UTC (rev 10768)
@@ -0,0 +1,19 @@
+errors: 0
+
+errors: 1
+
+errors: 1
+
+leaked: 0 bytes in 0 blocks
+dubious: 0 bytes in 0 blocks
+reachable: 0 bytes in 0 blocks
+suppressed: 0 bytes in 0 blocks
+
+errors: 1
+
+leaked: 77 bytes in 1 blocks
+dubious: 88 bytes in 1 blocks
+reachable: 99 bytes in 1 blocks
+suppressed: 0 bytes in 0 blocks
+
+errors: 3
Deleted: trunk/memcheck/tests/error_counts.stdout.exp
===================================================================
--- trunk/memcheck/tests/error_counts.stdout.exp 2009-08-10 07:50:00 UTC (rev 10767)
+++ trunk/memcheck/tests/error_counts.stdout.exp 2009-08-10 08:25:39 UTC (rev 10768)
@@ -1,15 +0,0 @@
-errors: 0
-
-errors: 1
-
-leaked: 0 bytes in 0 blocks
-dubious: 0 bytes in 0 blocks
-reachable: 0 bytes in 0 blocks
-suppressed: 0 bytes in 0 blocks
-
-leaked: 77 bytes in 1 blocks
-dubious: 88 bytes in 1 blocks
-reachable: 99 bytes in 1 blocks
-suppressed: 0 bytes in 0 blocks
-
-errors: 10
|
|
From: <sv...@va...> - 2009-08-10 07:50:11
|
Author: njn
Date: 2009-08-10 08:50:00 +0100 (Mon, 10 Aug 2009)
New Revision: 10767
Log:
Count leak as errors. Fixes bug 152393.
Modified:
trunk/coregrind/m_errormgr.c
trunk/include/pub_tool_errormgr.h
trunk/memcheck/mc_errors.c
trunk/memcheck/tests/error_counts.stdout.exp
Modified: trunk/coregrind/m_errormgr.c
===================================================================
--- trunk/coregrind/m_errormgr.c 2009-08-10 07:47:43 UTC (rev 10766)
+++ trunk/coregrind/m_errormgr.c 2009-08-10 07:50:00 UTC (rev 10767)
@@ -737,11 +737,10 @@
guaranteed to only happen once. This avoids all the recording and
comparing stuff. But they can be suppressed; returns True if it is
suppressed. Bool 'print_error' dictates whether to print the error.
- Bool 'count_error' dictates whether to count the error in n_errs_found.
*/
Bool VG_(unique_error) ( ThreadId tid, ErrorKind ekind, Addr a, Char* s,
void* extra, ExeContext* where, Bool print_error,
- Bool allow_db_attach, Bool count_error )
+ Bool allow_db_attach )
{
Error err;
Supp *su;
@@ -760,8 +759,7 @@
su = is_suppressible_error(&err);
if (NULL == su) {
- if (count_error)
- n_errs_found++;
+ n_errs_found++;
if (print_error) {
/* A bit of prettyprinting, to ensure there's a blank line
Modified: trunk/include/pub_tool_errormgr.h
===================================================================
--- trunk/include/pub_tool_errormgr.h 2009-08-10 07:47:43 UTC (rev 10766)
+++ trunk/include/pub_tool_errormgr.h 2009-08-10 07:50:00 UTC (rev 10767)
@@ -85,7 +85,7 @@
extern Bool VG_(unique_error) ( ThreadId tid, ErrorKind ekind,
Addr a, Char* s, void* extra,
ExeContext* where, Bool print_error,
- Bool allow_GDB_attach, Bool count_error );
+ Bool allow_GDB_attach );
/* Gets a non-blank, non-comment line from fd. bufpp is a pointer to a
pointer to a buffer that must be allocated with VG_(malloc); nBufp is a
Modified: trunk/memcheck/mc_errors.c
===================================================================
--- trunk/memcheck/mc_errors.c 2009-08-10 07:47:43 UTC (rev 10766)
+++ trunk/memcheck/mc_errors.c 2009-08-10 07:50:00 UTC (rev 10767)
@@ -951,7 +951,7 @@
return
VG_(unique_error) ( tid, Err_Leak, /*Addr*/0, /*s*/NULL, &extra,
lr->key.allocated_at, print_record,
- /*allow_GDB_attach*/False, /*count_error*/False );
+ /*allow_GDB_attach*/False );
}
void MC_(record_user_error) ( ThreadId tid, Addr a,
Modified: trunk/memcheck/tests/error_counts.stdout.exp
===================================================================
--- trunk/memcheck/tests/error_counts.stdout.exp 2009-08-10 07:47:43 UTC (rev 10766)
+++ trunk/memcheck/tests/error_counts.stdout.exp 2009-08-10 07:50:00 UTC (rev 10767)
@@ -12,4 +12,4 @@
reachable: 99 bytes in 1 blocks
suppressed: 0 bytes in 0 blocks
-errors: 1
+errors: 10
|
|
From: <sv...@va...> - 2009-08-10 07:48:00
|
Author: njn Date: 2009-08-10 08:47:43 +0100 (Mon, 10 Aug 2009) New Revision: 10766 Log: Remove unnecessary #includes. Modified: trunk/drd/drd_segment.c trunk/drd/drd_thread.c Modified: trunk/drd/drd_segment.c =================================================================== --- trunk/drd/drd_segment.c 2009-08-10 07:36:54 UTC (rev 10765) +++ trunk/drd/drd_segment.c 2009-08-10 07:47:43 UTC (rev 10766) @@ -27,7 +27,6 @@ #include "drd_segment.h" #include "drd_thread.h" #include "pub_tool_basics.h" // Addr, SizeT -#include "pub_tool_errormgr.h" // VG_(unique_error)() #include "pub_tool_libcassert.h" // tl_assert() #include "pub_tool_libcbase.h" // VG_(strlen)() #include "pub_tool_libcprint.h" // VG_(printf)() Modified: trunk/drd/drd_thread.c =================================================================== --- trunk/drd/drd_thread.c 2009-08-10 07:36:54 UTC (rev 10765) +++ trunk/drd/drd_thread.c 2009-08-10 07:47:43 UTC (rev 10766) @@ -34,7 +34,6 @@ #include "drd_thread.h" #include "pub_tool_vki.h" #include "pub_tool_basics.h" // Addr, SizeT -#include "pub_tool_errormgr.h" // VG_(unique_error)() #include "pub_tool_libcassert.h" // tl_assert() #include "pub_tool_libcbase.h" // VG_(strlen)() #include "pub_tool_libcprint.h" // VG_(printf)() |
|
From: Bart V. A. <bar...@gm...> - 2009-08-10 07:40:01
|
Nightly build on georgia-tech-cellbuzz-native ( cellbuzz, ppc64, Fedora 7, native ) Started at 2009-08-10 02:00:05 EDT Ended at 2009-08-10 03:39:35 EDT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... done Regression test results follow == 437 tests, 45 stderr failures, 9 stdout failures, 0 post failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cases-full (stderr) memcheck/tests/leak-cases-summary (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/varinfo1 (stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo3 (stderr) memcheck/tests/varinfo4 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/wrap8 (stderr) none/tests/empty-exe (stderr) none/tests/linux/mremap (stderr) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-vmx (stdout) none/tests/ppc32/round (stdout) none/tests/ppc32/test_gx (stdout) none/tests/ppc64/jm-fp (stdout) none/tests/ppc64/jm-vmx (stdout) none/tests/ppc64/round (stdout) none/tests/shell (stdout) none/tests/shell (stderr) none/tests/shell_valid1 (stderr) none/tests/shell_valid2 (stderr) none/tests/shell_valid3 (stderr) none/tests/shell_zerolength (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc06_two_races_xml (stderr) helgrind/tests/tc22_exit_w_lock (stderr) helgrind/tests/tc23_bogus_condwait (stderr) exp-ptrcheck/tests/bad_percentify (stderr) exp-ptrcheck/tests/base (stderr) exp-ptrcheck/tests/ccc (stderr) exp-ptrcheck/tests/fp (stderr) exp-ptrcheck/tests/globalerr (stderr) exp-ptrcheck/tests/hackedbz2 (stderr) exp-ptrcheck/tests/hp_bounds (stderr) exp-ptrcheck/tests/hp_dangle (stderr) exp-ptrcheck/tests/hsg (stderr) exp-ptrcheck/tests/justify (stderr) exp-ptrcheck/tests/partial_bad (stderr) exp-ptrcheck/tests/partial_good (stderr) exp-ptrcheck/tests/preen_invars (stderr) exp-ptrcheck/tests/pth_create (stderr) exp-ptrcheck/tests/pth_specific (stderr) exp-ptrcheck/tests/realloc (stderr) exp-ptrcheck/tests/stackerr (stderr) exp-ptrcheck/tests/strcpy (stderr) exp-ptrcheck/tests/supp (stderr) exp-ptrcheck/tests/tricky (stderr) exp-ptrcheck/tests/unaligned (stderr) exp-ptrcheck/tests/zero (stderr) |
|
From: <sv...@va...> - 2009-08-10 07:37:06
|
Author: njn
Date: 2009-08-10 08:36:54 +0100 (Mon, 10 Aug 2009)
New Revision: 10765
Log:
Allow custom blocks to overlap with malloc blocks. Fixes bug 100628.
Added:
trunk/memcheck/tests/custom-overlap.c
trunk/memcheck/tests/custom-overlap.stderr.exp
trunk/memcheck/tests/custom-overlap.vgtest
Modified:
trunk/coregrind/m_hashtable.c
trunk/include/pub_tool_hashtable.h
trunk/include/valgrind.h
trunk/memcheck/mc_include.h
trunk/memcheck/mc_leakcheck.c
trunk/memcheck/tests/Makefile.am
Modified: trunk/coregrind/m_hashtable.c
===================================================================
--- trunk/coregrind/m_hashtable.c 2009-08-10 06:47:00 UTC (rev 10764)
+++ trunk/coregrind/m_hashtable.c 2009-08-10 07:36:54 UTC (rev 10765)
@@ -138,7 +138,7 @@
}
/* Puts a new, heap allocated VgHashNode, into the VgHashTable. Prepends
- the node to the appropriate chain. */
+ the node to the appropriate chain. No duplicate key detection is done. */
void VG_(HT_add_node) ( VgHashTable table, void* vnode )
{
VgHashNode* node = (VgHashNode*)vnode;
Modified: trunk/include/pub_tool_hashtable.h
===================================================================
--- trunk/include/pub_tool_hashtable.h 2009-08-10 06:47:00 UTC (rev 10764)
+++ trunk/include/pub_tool_hashtable.h 2009-08-10 07:36:54 UTC (rev 10765)
@@ -58,10 +58,12 @@
/* Count the number of nodes in a table. */
extern Int VG_(HT_count_nodes) ( VgHashTable table );
-/* Add a node to the table. */
+/* Add a node to the table. Duplicate keys are permitted. */
extern void VG_(HT_add_node) ( VgHashTable t, void* node );
-/* Looks up a VgHashNode in the table. Returns NULL if not found. */
+/* Looks up a VgHashNode in the table. Returns NULL if not found. If entries
+ * with duplicate keys are present, the most recently-added of the dups will
+ * be returned, but it's probably better to avoid dups altogether. */
extern void* VG_(HT_lookup) ( VgHashTable table, UWord key );
/* Removes a VgHashNode from the table. Returns NULL if not found. */
Modified: trunk/include/valgrind.h
===================================================================
--- trunk/include/valgrind.h 2009-08-10 06:47:00 UTC (rev 10764)
+++ trunk/include/valgrind.h 2009-08-10 07:36:54 UTC (rev 10765)
@@ -3851,6 +3851,11 @@
stack traces relating to the heap block will contain entries for both
my_alloc() and internal_alloc(), which is probably not what you want.
+ For Memcheck users: if you use VALGRIND_MALLOCLIKE_BLOCK to carve out
+ custom blocks from within a heap block, B, that has been allocated with
+ malloc/calloc/new/etc, then block B will be *ignored* during leak-checking
+ -- the custom blocks will take precedence.
+
VALGRIND_FREELIKE_BLOCK is the partner to VALGRIND_MALLOCLIKE_BLOCK. For
Memcheck, it does two things:
@@ -3884,11 +3889,6 @@
Note: there is currently no VALGRIND_REALLOCLIKE_BLOCK client request; it
has to be emulated with MALLOCLIKE/FREELIKE and memory copying.
- WARNING: if your allocator uses malloc() or 'new' to allocate
- superblocks, rather than mmap() or brk(), this will not work properly --
- you'll likely get assertion failures during leak detection. This is
- because Valgrind doesn't like seeing overlapping heap blocks. Sorry.
-
Ignored if addr == 0.
*/
#define VALGRIND_MALLOCLIKE_BLOCK(addr, sizeB, rzB, is_zeroed) \
Modified: trunk/memcheck/mc_include.h
===================================================================
--- trunk/memcheck/mc_include.h 2009-08-10 06:47:00 UTC (rev 10764)
+++ trunk/memcheck/mc_include.h 2009-08-10 07:36:54 UTC (rev 10765)
@@ -98,7 +98,10 @@
MC_Chunk* MC_(get_freed_list_head)( void );
-/* For tracking malloc'd blocks */
+/* For tracking malloc'd blocks. Nb: it's quite important that it's a
+ VgHashTable, because VgHashTable allows duplicate keys without complaint.
+ This can occur if a user marks a malloc() block as also a custom block with
+ MALLOCLIKE_BLOCK. */
extern VgHashTable MC_(malloc_list);
/* For tracking memory pools. */
Modified: trunk/memcheck/mc_leakcheck.c
===================================================================
--- trunk/memcheck/mc_leakcheck.c 2009-08-10 06:47:00 UTC (rev 10764)
+++ trunk/memcheck/mc_leakcheck.c 2009-08-10 07:36:54 UTC (rev 10765)
@@ -910,7 +910,7 @@
void MC_(detect_memory_leaks) ( ThreadId tid, LeakCheckMode mode )
{
- Int i;
+ Int i, j;
tl_assert(mode != LC_Off);
@@ -933,27 +933,63 @@
tl_assert( lc_chunks[i]->data <= lc_chunks[i+1]->data);
}
- // Sanity check -- make sure they don't overlap. But do allow exact
- // duplicates. If this assertion fails, it may mean that the application
+ // Sanity check -- make sure they don't overlap. The one exception is that
+ // we allow a MALLOCLIKE block to sit entirely within a malloc() block.
+ // This is for bug 100628. If this occurs, we ignore the malloc() block
+ // for leak-checking purposes. This is a hack and probably should be done
+ // better, but at least it's consistent with mempools (which are treated
+ // like this in find_active_chunks). Mempools have a separate VgHashTable
+ // for mempool chunks, but if custom-allocated blocks are put in a separate
+ // table from normal heap blocks it makes free-mismatch checking more
+ // difficult.
+ //
+ // If this check fails, it probably means that the application
// has done something stupid with VALGRIND_MALLOCLIKE_BLOCK client
- // requests, specifically, has made overlapping requests (which are
- // nonsensical). Another way to screw up is to use
- // VALGRIND_MALLOCLIKE_BLOCK for stack locations; again nonsensical.
+ // requests, eg. has made overlapping requests (which are
+ // nonsensical), or used VALGRIND_MALLOCLIKE_BLOCK for stack locations;
+ // again nonsensical.
+ //
for (i = 0; i < lc_n_chunks-1; i++) {
MC_Chunk* ch1 = lc_chunks[i];
MC_Chunk* ch2 = lc_chunks[i+1];
- Bool nonsense_overlap = ! (
- // Normal case - no overlap.
- (ch1->data + ch1->szB <= ch2->data) ||
- // Degenerate case: exact duplicates.
- (ch1->data == ch2->data && ch1->szB == ch2->szB)
- );
- if (nonsense_overlap) {
- VG_(umsg)("Block [0x%lx, 0x%lx) overlaps with block [0x%lx, 0x%lx)\n",
- ch1->data, (ch1->data + ch1->szB),
- ch2->data, (ch2->data + ch2->szB));
+
+ Addr start1 = ch1->data;
+ Addr start2 = ch2->data;
+ Addr end1 = ch1->data + ch1->szB - 1;
+ Addr end2 = ch2->data + ch2->szB - 1;
+ Bool isCustom1 = ch1->allockind == MC_AllocCustom;
+ Bool isCustom2 = ch2->allockind == MC_AllocCustom;
+
+ if (end1 < start2) {
+ // Normal case - no overlap.
+
+ // We used to allow exact duplicates, I'm not sure why. --njn
+ //} else if (start1 == start2 && end1 == end2) {
+ // Degenerate case: exact duplicates.
+
+ } else if (start1 >= start2 && end1 <= end2 && isCustom1 && !isCustom2) {
+ // Block i is MALLOCLIKE and entirely within block i+1.
+ // Remove block i+1.
+ for (j = i+1; j < lc_n_chunks-1; j++) {
+ lc_chunks[j] = lc_chunks[j+1];
+ }
+ lc_n_chunks--;
+
+ } else if (start2 >= start1 && end2 <= end1 && isCustom2 && !isCustom1) {
+ // Block i+1 is MALLOCLIKE and entirely within block i.
+ // Remove block i.
+ for (j = i; j < lc_n_chunks-1; j++) {
+ lc_chunks[j] = lc_chunks[j+1];
+ }
+ lc_n_chunks--;
+
+ } else {
+ VG_(umsg)("Block 0x%lx..0x%lx overlaps with block 0x%lx..0x%lx",
+ start1, end1, start1, end2);
+ VG_(umsg)("This is usually caused by using VALGRIND_MALLOCLIKE_BLOCK");
+ VG_(umsg)("in an inappropriate way.");
+ tl_assert (0);
}
- tl_assert (!nonsense_overlap);
}
// Initialise lc_extras.
Modified: trunk/memcheck/tests/Makefile.am
===================================================================
--- trunk/memcheck/tests/Makefile.am 2009-08-10 06:47:00 UTC (rev 10764)
+++ trunk/memcheck/tests/Makefile.am 2009-08-10 07:36:54 UTC (rev 10765)
@@ -53,6 +53,7 @@
clientperm.stderr.exp \
clientperm.stdout.exp clientperm.vgtest \
custom_alloc.stderr.exp custom_alloc.vgtest \
+ custom-overlap.stderr.exp custom-overlap.vgtest \
deep_templates.vgtest \
deep_templates.stdout.exp deep_templates.stderr.exp \
describe-block.stderr.exp describe-block.vgtest \
@@ -191,6 +192,7 @@
calloc-overflow \
clientperm \
custom_alloc \
+ custom-overlap \
deep_templates \
describe-block \
doublefree error_counts errs1 exitprog execve execve2 erringfds \
Added: trunk/memcheck/tests/custom-overlap.c
===================================================================
--- trunk/memcheck/tests/custom-overlap.c (rev 0)
+++ trunk/memcheck/tests/custom-overlap.c 2009-08-10 07:36:54 UTC (rev 10765)
@@ -0,0 +1,28 @@
+// Test for bug 100628: need to allow custom MALLOCLIKE blocks to overlap
+// with normal malloc() blocks in leak-checking -- if it happens, we ignore
+// the malloc() block during the leak check.
+
+#include <stdlib.h>
+#include "valgrind.h"
+
+int main(void)
+{
+ char* x;
+
+ // For this one, the first custom block overlaps exactly with the start of
+ // the malloc block.
+ x = malloc(1000);
+ VALGRIND_MALLOCLIKE_BLOCK(x, /*szB*/ 16, /*rzB*/0, /*isZeroed*/0);
+ VALGRIND_MALLOCLIKE_BLOCK(x+100, /*szB*/ 32, /*rzB*/0, /*isZeroed*/0);
+ VALGRIND_MALLOCLIKE_BLOCK(x+200, /*szB*/ 64, /*rzB*/0, /*isZeroed*/0);
+ VALGRIND_MALLOCLIKE_BLOCK(x+300, /*szB*/128, /*rzB*/0, /*isZeroed*/0);
+
+ // For this one, the first custom block does not overlap exactly with the
+ // start of the malloc block.
+ x = malloc(1000);
+ VALGRIND_MALLOCLIKE_BLOCK(x+100, /*szB*/ 32, /*rzB*/0, /*isZeroed*/0);
+ VALGRIND_MALLOCLIKE_BLOCK(x+200, /*szB*/ 64, /*rzB*/0, /*isZeroed*/0);
+ VALGRIND_MALLOCLIKE_BLOCK(x+300, /*szB*/128, /*rzB*/0, /*isZeroed*/0);
+
+ return 0;
+}
Added: trunk/memcheck/tests/custom-overlap.stderr.exp
===================================================================
Added: trunk/memcheck/tests/custom-overlap.vgtest
===================================================================
--- trunk/memcheck/tests/custom-overlap.vgtest (rev 0)
+++ trunk/memcheck/tests/custom-overlap.vgtest 2009-08-10 07:36:54 UTC (rev 10765)
@@ -0,0 +1,2 @@
+prog: custom-overlap
+vgopts: --leak-check=summary -q
|
|
From: <sv...@va...> - 2009-08-10 06:47:13
|
Author: njn Date: 2009-08-10 07:47:00 +0100 (Mon, 10 Aug 2009) New Revision: 10764 Log: augment a comment Modified: trunk/memcheck/mc_leakcheck.c Modified: trunk/memcheck/mc_leakcheck.c =================================================================== --- trunk/memcheck/mc_leakcheck.c 2009-08-10 05:11:43 UTC (rev 10763) +++ trunk/memcheck/mc_leakcheck.c 2009-08-10 06:47:00 UTC (rev 10764) @@ -113,6 +113,7 @@ // ---- // // Also, why are two blank lines printed between each loss record? +// [bug 197930] // // ---- // |
|
From: Nicholas N. <n.n...@gm...> - 2009-08-10 06:37:18
|
Hi, I'm looking at bug 197930 (https://bugs.kde.org/show_bug.cgi?id=197930) which seems simple, but fixing it requires fixing our rather ad hoc treatment of blank lines in the output. Current we put blank lines in various places: - at the end of the preamble - at the start of the postamble - before an error message, unless it's the first error message - before various other places It's ugly and messy, and the "unless" bit works fine so long as an error message is preceded by another error message, but otherwise we hit problems. In particular, leak errors are printed after the HEAP SUMMARY and whether we get a blank line or not depends on whether other errors were found earlier. So leak errors print an additional blank line to ensure that there's at least one after the HEAP SUMMARY, but this means that there are always two between each leak error. I propose a reworking that will fix 197930 and will make things a lot simpler. It involves establishing the following invariants: - print a blank at the end of the preamble (just like now) - print a blank at the start of the postamble (just like now) - for any significant user message, the code emitting the message should emit a blank line at its end. This makes the messaging code a lot simpler. One consequence can be seen in the output of memcheck/tests/manuel1.c (and a lot of others, this is just an example) which currently looks like this: ==23388== Memcheck, a memory error detector. ==23388== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==23388== Using Valgrind-3.5.0.SVN and LibVEX; rerun with -h for copyright info ==23388== Command: memcheck/tests/manuel1 ==23388== ==23388== Conditional jump or move depends on uninitialised value(s) ==23388== at 0x40051B: main (manuel1.c:7) ==23388== ==23388== HEAP SUMMARY: ==23388== in use at exit: 0 bytes in 0 blocks. ==23388== total heap usage: 0 allocs, 0 frees, 0 bytes allocated. ==23388== ==23388== All heap blocks were freed -- no leaks are possible. ==23388== ==23388== For counts of detected and suppressed errors, rerun with: -v ==23388== Use --track-origins=yes to see where uninitialised values come from ==23388== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 8 from 1) With my proposed change there would be two blanks lines before the HEAP SUMMARY -- one after the error message, and one at the start of the postamble. That arguably makes it consistent with the no-error case, which currently looks like this (and would be the same with my proposal): ==23388== Command: memcheck/tests/manuel1 ==23388== ==23388== ==23388== HEAP SUMMARY: There are lots of regtest changes required with my proposal because with -q there's always a blank line printed after every error, which wasn't the case before. I don't think this is a big concern. Thoughts? Another possibility is to just get rid of the blank line at the start of the postamble, which requires more regtest .exp changes but is arguably even more consistent. The current approach, which attempts to avoid unnecessary blank lines, is admirable in its aim but is complex and doesn't work properly. It could be fixed up like this: - print a blank at the end of the preamble (just like now) - print a blank at the start of the postamble (just like now) - for any significant user message, the code emitting the message should emit a blank line at its start if any significant messages have been printed before. Things like the HEAP SUMMARY would count as significant messages. This is basically following the current design, but doing it properly. It would be a lot more complicated and fragile than my proposal above because you'd have to always record the fact that significant messages have been printed, and that would require touching a lot of places. In fact, I had a go at it but it's difficult to get working in all cases because of the need to always have the blank line at the start of the post-amble. N |
|
From: <sv...@va...> - 2009-08-10 05:11:57
|
Author: njn Date: 2009-08-10 06:11:43 +0100 (Mon, 10 Aug 2009) New Revision: 10763 Log: add an item Modified: trunk/NEWS Modified: trunk/NEWS =================================================================== --- trunk/NEWS 2009-08-10 04:07:54 UTC (rev 10762) +++ trunk/NEWS 2009-08-10 05:11:43 UTC (rev 10763) @@ -46,6 +46,8 @@ ==3050== Command: ls -l ==3050== +* XXX: shut-down messages have changed a bit... + * A new Memcheck client request VALGRIND_COUNT_LEAK_BLOCKS has been added. It is similar to VALGRIND_COUNT_LEAKS but counts blocks instead of bytes. [XXX: consider adding VALGRIND_COUNT_LEAK_BYTES as a synonym and |
|
From: <sv...@va...> - 2009-08-10 04:08:10
|
Author: njn Date: 2009-08-10 05:07:54 +0100 (Mon, 10 Aug 2009) New Revision: 10762 Log: wibble Modified: trunk/memcheck/docs/mc-manual.xml Modified: trunk/memcheck/docs/mc-manual.xml =================================================================== --- trunk/memcheck/docs/mc-manual.xml 2009-08-10 01:43:20 UTC (rev 10761) +++ trunk/memcheck/docs/mc-manual.xml 2009-08-10 04:07:54 UTC (rev 10762) @@ -1339,7 +1339,7 @@ -<sect1 id="mc-manual.mempools" xreflabel="Memory pools"> +<sect1 id="mc-manual.mempools" xreflabel="Memory Pools"> <title>Memory Pools: describing and working with custom allocators</title> <para>Some programs use custom memory allocators, often for performance |
|
From: Tom H. <th...@cy...> - 2009-08-10 02:47:56
|
Nightly build on lloyd ( x86_64, Fedora 7 ) Started at 2009-08-10 03:05:03 BST Ended at 2009-08-10 03:47:38 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 520 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) |
|
From: Tom H. <th...@cy...> - 2009-08-10 02:31:07
|
Nightly build on mg ( x86_64, Fedora 9 ) Started at 2009-08-10 03:10:05 BST Ended at 2009-08-10 03:30:50 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 527 tests, 1 stderr failure, 0 stdout failures, 0 post failures == helgrind/tests/tc06_two_races_xml (stderr) |
|
From: <sv...@va...> - 2009-08-10 01:58:49
|
Author: njn
Date: 2009-08-10 02:43:20 +0100 (Mon, 10 Aug 2009)
New Revision: 10761
Log:
Remove bad explanations of mempool requests from the core manual, just point
to the Memcheck chapter.
Modified:
trunk/docs/xml/manual-core-adv.xml
Modified: trunk/docs/xml/manual-core-adv.xml
===================================================================
--- trunk/docs/xml/manual-core-adv.xml 2009-08-10 01:34:27 UTC (rev 10760)
+++ trunk/docs/xml/manual-core-adv.xml 2009-08-10 01:43:20 UTC (rev 10761)
@@ -152,47 +152,25 @@
</varlistentry>
<varlistentry>
- <term><command><computeroutput>VALGRIND_CREATE_MEMPOOL</computeroutput>:</command></term>
+ <term>
+ <command><computeroutput>VALGRIND_CREATE_MEMPOOL</computeroutput></command>,
+ <command><computeroutput>VALGRIND_DESTROY_MEMPOOL</computeroutput></command>,
+ <command><computeroutput>VALGRIND_MEMPOOL_ALLOC</computeroutput></command>,
+ <command><computeroutput>VALGRIND_MEMPOOL_FREE</computeroutput></command>,
+ <command><computeroutput>VALGRIND_MOVE_MEMPOOL</computeroutput></command>,
+ <command><computeroutput>VALGRIND_MEMPOOL_CHANGE</computeroutput></command>,
+ <command><computeroutput>VALGRIND_MEMPOOL_EXISTS</computeroutput></command>:
+ </term>
<listitem>
- <para>This is similar to
- <computeroutput>VALGRIND_MALLOCLIKE_BLOCK</computeroutput>,
- but is tailored towards code that uses memory pools. See the
- comments in <filename>valgrind.h</filename> for information
- on how to use it.</para>
+ <para>These are similar to
+ <computeroutput>VALGRIND_MALLOCLIKE_BLOCK</computeroutput> and
+ <computeroutput>VALGRIND_FREELIKE_BLOCK</computeroutput>
+ but are tailored towards code that uses memory pools. See
+ <xref linkend="mc-manual.mempools"/> for a detailed description.</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><command><computeroutput>VALGRIND_DESTROY_MEMPOOL</computeroutput>:</command></term>
- <listitem>
- <para>This should be used in conjunction with
- <computeroutput>VALGRIND_CREATE_MEMPOOL</computeroutput>.
- Again, see the comments in <filename>valgrind.h</filename> for
- information on how to use it.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><command><computeroutput>VALGRIND_MEMPOOL_ALLOC</computeroutput>:</command></term>
- <listitem>
- <para>This should be used in conjunction with
- <computeroutput>VALGRIND_CREATE_MEMPOOL</computeroutput>.
- Again, see the comments in <filename>valgrind.h</filename> for
- information on how to use it.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term><command><computeroutput>VALGRIND_MEMPOOL_FREE</computeroutput>:</command></term>
- <listitem>
- <para>This should be used in conjunction with
- <computeroutput>VALGRIND_CREATE_MEMPOOL</computeroutput>.
- Again, see the comments in <filename>valgrind.h</filename> for
- information on how to use it.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term><command><computeroutput>VALGRIND_NON_SIMD_CALL[0123]</computeroutput>:</command></term>
<listitem>
<para>Executes a function in the client program on the
|
|
From: <sv...@va...> - 2009-08-10 01:53:48
|
Author: njn
Date: 2009-08-10 02:34:27 +0100 (Mon, 10 Aug 2009)
New Revision: 10760
Log:
wibble
Modified:
trunk/drd/docs/drd-manual.xml
trunk/massif/docs/ms-manual.xml
Modified: trunk/drd/docs/drd-manual.xml
===================================================================
--- trunk/drd/docs/drd-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
+++ trunk/drd/docs/drd-manual.xml 2009-08-10 01:34:27 UTC (rev 10760)
@@ -1073,6 +1073,14 @@
name in the error messages printed by DRD.
</para>
</listitem>
+ <listitem>
+ <para>
+ The macros <literal>VALGRIND_MALLOCLIKE_BLOCK</literal> and
+ <literal>VALGRIND_FREELIKE_BLOCK</literal> from the Valgrind core are
+ implemented; they are described in
+ <xref linkend="manual-core-adv.clientreq"/>.
+ </para>
+ </listitem>
</itemizedlist>
</para>
Modified: trunk/massif/docs/ms-manual.xml
===================================================================
--- trunk/massif/docs/ms-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
+++ trunk/massif/docs/ms-manual.xml 2009-08-10 01:34:27 UTC (rev 10760)
@@ -818,8 +818,9 @@
<para>Massif does not have a <filename>massif.h</filename> file, but it does
implement two of the core client requests:
<function>VALGRIND_MALLOCLIKE_BLOCK</function> and
-<function>VALGRIND_FREELIKE_BLOCK</function>. These work in the obvious
-way.</para>
+<function>VALGRIND_FREELIKE_BLOCK</function>; they are described in
+<xref linkend="manual-core-adv.clientreq"/>.
+</para>
</sect1>
|
Author: njn
Date: 2009-08-10 02:29:14 +0100 (Mon, 10 Aug 2009)
New Revision: 10759
Log:
Make "option" terminology consistent some more. Also tweaked the mempool
Memcheck section a little.
Modified:
trunk/cachegrind/docs/cg-manual.xml
trunk/callgrind/docs/cl-manual.xml
trunk/coregrind/m_main.c
trunk/drd/docs/drd-manual.xml
trunk/exp-bbv/docs/bbv-manual.xml
trunk/exp-ptrcheck/docs/pc-manual.xml
trunk/helgrind/docs/hg-manual.xml
trunk/lackey/docs/lk-manual.xml
trunk/massif/docs/ms-manual.xml
trunk/memcheck/docs/mc-manual.xml
Modified: trunk/cachegrind/docs/cg-manual.xml
===================================================================
--- trunk/cachegrind/docs/cg-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/cachegrind/docs/cg-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -90,7 +90,7 @@
<para>First off, as for normal Valgrind use, you probably want to
compile with debugging info (the
-<option>-g</option> flag). But by contrast with
+<option>-g</option> option). But by contrast with
normal Valgrind use, you probably do want to turn
optimisation on, since you should profile your program as it will
be normally run.</para>
@@ -151,7 +151,7 @@
</para>
<para>Branch prediction statistics are not collected by default.
-To do so, add the flag <option>--branch-sim=yes</option>.</para>
+To do so, add the option <option>--branch-sim=yes</option>.</para>
</sect2>
@@ -703,8 +703,8 @@
-<sect1 id="cg-manual.cgopts" xreflabel="Cachegrind Options">
-<title>Cachegrind Options</title>
+<sect1 id="cg-manual.cgopts" xreflabel="Cachegrind Command-line Options">
+<title>Cachegrind Command-line Options</title>
<!-- start of xi:include in the manpage -->
<para>Cachegrind-specific options are:</para>
@@ -790,8 +790,8 @@
-<sect1 id="cg-manual.annopts" xreflabel="cg_annotate Options">
-<title>cg_annotate Options</title>
+<sect1 id="cg-manual.annopts" xreflabel="cg_annotate Command-line Options">
+<title>cg_annotate Command-line Options</title>
<!-- start of xi:include in the manpage -->
<variablelist id="cg_annotate.opts.list">
Modified: trunk/callgrind/docs/cl-manual.xml
===================================================================
--- trunk/callgrind/docs/cl-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/callgrind/docs/cl-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -46,10 +46,10 @@
<term><command>callgrind_control</command></term>
<listitem>
<para>This command enables you to interactively observe and control
- the status of currently running applications, without stopping
- the application. You can
- get statistics information as well as the current stack trace, and
- you can request zeroing of counters or dumping of profile data.</para>
+ the status of a program currently running under Callgrind's control,
+ without stopping the program. You can get statistics information as
+ well as the current stack trace, and you can request zeroing of counters
+ or dumping of profile data.</para>
</listitem>
</varlistentry>
</variablelist>
@@ -105,7 +105,7 @@
<title>Basic Usage</title>
<para>As with Cachegrind, you probably want to compile with debugging info
- (the <option>-g</option> flag) and with optimization turned on.</para>
+ (the <option>-g</option> option) and with optimization turned on.</para>
<para>To start a profile run for a program, execute:
<screen>valgrind --tool=callgrind [callgrind options] your-program [program options]</screen>
@@ -476,15 +476,15 @@
intermingled, which almost certainly is not what you want.</para>
<para>You will be able to control the new child independently from
- the parent via <computeroutput>callgrind_control</computeroutput>.</para>
+ the parent via callgrind_control.</para>
</sect2>
</sect1>
-<sect1 id="cl-manual.options" xreflabel="Callgrind Options">
-<title>Callgrind Options</title>
+<sect1 id="cl-manual.options" xreflabel="Callgrind Command-line Options">
+<title>Callgrind Command-line Options</title>
<para>
In the following, options are grouped into classes.
@@ -600,8 +600,7 @@
<para>
These options specify when actions relating to event counts are to
-be executed. For interactive control use
-<computeroutput>callgrind_control</computeroutput>.
+be executed. For interactive control use callgrind_control.
</para>
<!-- start of xi:include in the manpage -->
@@ -716,7 +715,7 @@
<para>Collection state can be
toggled at entry and exit of a given function with the
option <option><xref linkend="opt.toggle-collect"/></option>. If you
- use this flag, collection
+ use this option, collection
state should be disabled at the beginning. Note that the
specification of <option>--toggle-collect</option>
implicitly sets
@@ -1104,8 +1103,8 @@
-<sect1 id="cl-manual.callgrind_annotate-options" xreflabel="callgrind_annotate Options">
-<title>callgrind_annotate Options</title>
+<sect1 id="cl-manual.callgrind_annotate-options" xreflabel="callgrind_annotate Command-line Options">
+<title>callgrind_annotate Command-line Options</title>
<!-- start of xi:include in the manpage -->
<variablelist id="callgrind_annotate.opts.list">
@@ -1210,16 +1209,14 @@
-<sect1 id="cl-manual.callgrind_control-options" xreflabel="callgrind_control Options">
-<title>Description and options of callgrind_control</title>
+<sect1 id="cl-manual.callgrind_control-options" xreflabel="callgrind_control Command-line Options">
+<title>callgrind_control Command-line Options</title>
-<para>The command <command>callgrind_control</command> allows to control
- programs being run by the Valgrind tool Callgrind. By default, it acts
- on all programs detected to be run by the current user via Callgrind.
- It is possible to limit the actions to specified Callgrind runs by
- providing a list of pids or program names as argument.
- The default action is to give some brief information about the applications
- being run by Callgrind.</para>
+<para>By default, callgrind_control acts on all programs run by the
+ current user under Callgrind. It is possible to limit the actions to
+ specified Callgrind runs by providing a list of pids or program names as
+ argument. The default action is to give some brief information about the
+ applications being run under Callgrind.</para>
<!-- start of xi:include in the manpage -->
<variablelist id="callgrind_control.opts.list">
Modified: trunk/coregrind/m_main.c
===================================================================
--- trunk/coregrind/m_main.c 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/coregrind/m_main.c 2009-08-10 01:29:14 UTC (rev 10759)
@@ -1123,7 +1123,7 @@
VexArchInfo vex_archinfo;
if (!logging_to_fd)
VG_(message)(Vg_DebugMsg, "\n");
- VG_(message)(Vg_DebugMsg, "Valgrind flags:\n");
+ VG_(message)(Vg_DebugMsg, "Valgrind options:\n");
for (i = 0; i < VG_(sizeXA)( VG_(args_for_valgrind) ); i++) {
VG_(message)(Vg_DebugMsg,
" %s\n",
Modified: trunk/drd/docs/drd-manual.xml
===================================================================
--- trunk/drd/docs/drd-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/drd/docs/drd-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -315,8 +315,8 @@
<sect1 id="drd-manual.using-drd" xreflabel="Using DRD">
<title>Using DRD</title>
-<sect2 id="drd-manual.options" xreflabel="DRD Options">
-<title>Command Line Options</title>
+<sect2 id="drd-manual.options" xreflabel="DRD Command-line Options">
+<title>DRD Command-line Options</title>
<para>The following command-line options are available for controlling the
behavior of the DRD tool itself:</para>
@@ -1211,8 +1211,8 @@
<literal>libgomp</literal>. The synchronization primitives implemented
in this library use Linux' futex system call directly, unless the
library has been configured with the
-<literal>--disable-linux-futex</literal> flag. DRD only supports
-libgomp libraries that have been configured with this flag and in
+<literal>--disable-linux-futex</literal> option. DRD only supports
+libgomp libraries that have been configured with this option and in
which symbol information is present. For most Linux distributions this
means that you will have to recompile GCC. See also the script
<literal>drd/scripts/download-and-build-gcc</literal> in the
@@ -1416,7 +1416,7 @@
</listitem>
<listitem>
<para>
- Compile with flag <option>-O1</option> instead of
+ Compile with option <option>-O1</option> instead of
<option>-O0</option>. This will reduce the amount of generated
code, may reduce the amount of debug info and will speed up
DRD's processing of the client program. For more information,
Modified: trunk/exp-bbv/docs/bbv-manual.xml
===================================================================
--- trunk/exp-bbv/docs/bbv-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/exp-bbv/docs/bbv-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -110,10 +110,10 @@
</sect1>
-<sect1 id="bbv-manual.usage" xreflabel="BBV Usage">
-<title>BBV Command Line Options</title>
+<sect1 id="bbv-manual.usage" xreflabel="BBV Command-line Options">
+<title>BBV Command-line Options</title>
-<para> BBV-specific options are:</para>
+<para> BBV-specific command-line options are:</para>
<!-- start of xi:include in the manpage -->
<variablelist id="bbv.opts.list">
Modified: trunk/exp-ptrcheck/docs/pc-manual.xml
===================================================================
--- trunk/exp-ptrcheck/docs/pc-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/exp-ptrcheck/docs/pc-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -46,10 +46,10 @@
-<sect1 id="pc-manual.options" xreflabel="Ptrcheck Options">
-<title>Ptrcheck Options</title>
+<sect1 id="pc-manual.options" xreflabel="Ptrcheck Command-line Options">
+<title>Ptrcheck Command-line Options</title>
-<para>Ptrcheck-specific options are:</para>
+<para>Ptrcheck-specific command-line options are:</para>
<!-- start of xi:include in the manpage -->
<variablelist id="pc.opts.list">
@@ -89,7 +89,7 @@
</para>
<para>Note that code that behaves in this way is in violation of
the the ISO C/C++ standards, and should be considered broken. If
- at all possible, such code should be fixed. This flag should be
+ at all possible, such code should be fixed. This option should be
used only as a last resort.</para>
</listitem>
</varlistentry>
Modified: trunk/helgrind/docs/hg-manual.xml
===================================================================
--- trunk/helgrind/docs/hg-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/helgrind/docs/hg-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -351,7 +351,7 @@
However, it does require Helgrind to spend considerable extra time
and memory at program startup to read the relevant debug info.
Hence this facility is disabled by default. To enable it, you need
- to give the <varname>--read-var-info=yes</varname> flag to
+ to give the <varname>--read-var-info=yes</varname> option to
Helgrind.</para>
</listitem>
</itemizedlist>
@@ -745,7 +745,7 @@
instructions and the futex syscall, which causes total chaos since in
Helgrind since it cannot "see" those.</para>
<para>Fortunately, this can be solved using a configuration-time
- flag (for GCC). Rebuild GCC from source, and configure using
+ option (for GCC). Rebuild GCC from source, and configure using
<varname>--disable-linux-futex</varname>.
This makes libgomp.so use the standard
POSIX threading primitives instead. Note that this was tested
@@ -938,8 +938,8 @@
-<sect1 id="hg-manual.options" xreflabel="Helgrind Options">
-<title>Helgrind Options</title>
+<sect1 id="hg-manual.options" xreflabel="Helgrind Command-line Options">
+<title>Helgrind Command-line Options</title>
<para>The following end-user options are available:</para>
@@ -1000,7 +1000,7 @@
for every single memory access made by the program.
Historical information on not recently accessed locations is
periodically discarded, to free up space in the cache.</para>
- <para>This flag controls the size of the cache, in terms of the
+ <para>This option controls the size of the cache, in terms of the
number of different memory addresses for which
conflicting access information is stored. If you find that
Helgrind is showing race errors with only one stack instead of
Modified: trunk/lackey/docs/lk-manual.xml
===================================================================
--- trunk/lackey/docs/lk-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/lackey/docs/lk-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -23,10 +23,10 @@
</sect1>
-<sect1 id="lk-manual.options" xreflabel="Lackey Options">
-<title>Lackey Options</title>
+<sect1 id="lk-manual.options" xreflabel="Lackey Command-line Options">
+<title>Lackey Command-line Options</title>
-<para>Lackey-specific options are:</para>
+<para>Lackey-specific command-line options are:</para>
<!-- start of xi:include in the manpage -->
<variablelist id="lk.opts.list">
Modified: trunk/massif/docs/ms-manual.xml
===================================================================
--- trunk/massif/docs/ms-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/massif/docs/ms-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -53,7 +53,7 @@
<title>Using Massif and ms_print</title>
<para>First off, as for the other Valgrind tools, you should compile with
-debugging info (the <option>-g</option> flag). It shouldn't
+debugging info (the <option>-g</option> option). It shouldn't
matter much what optimisation level you compile your program with, as this
is unlikely to affect the heap memory usage.</para>
@@ -606,10 +606,10 @@
</sect1>
-<sect1 id="ms-manual.options" xreflabel="Massif Options">
-<title>Massif Options</title>
+<sect1 id="ms-manual.options" xreflabel="Massif Command-line Options">
+<title>Massif Command-line Options</title>
-<para>Massif-specific options are:</para>
+<para>Massif-specific command-line options are:</para>
<!-- start of xi:include in the manpage -->
<variablelist id="ms.opts.list">
@@ -824,8 +824,8 @@
</sect1>
-<sect1 id="ms-manual.ms_print-options" xreflabel="ms_print Options">
-<title>ms_print Options</title>
+<sect1 id="ms-manual.ms_print-options" xreflabel="ms_print Command-line Options">
+<title>ms_print Command-line Options</title>
<para>ms_print's options are:</para>
Modified: trunk/memcheck/docs/mc-manual.xml
===================================================================
--- trunk/memcheck/docs/mc-manual.xml 2009-08-10 01:15:30 UTC (rev 10758)
+++ trunk/memcheck/docs/mc-manual.xml 2009-08-10 01:29:14 UTC (rev 10759)
@@ -167,7 +167,7 @@
</itemizedlist>
<para>To see information on the sources of uninitialised data in your
-program, use the <option>--track-origins=yes</option> flag. This
+program, use the <option>--track-origins=yes</option> option. This
makes Memcheck run more slowly, but can make it much easier to track down
the root causes of uninitialised value errors.</para>
@@ -574,9 +574,9 @@
-<sect1 id="mc-manual.flags"
- xreflabel="Command-line flags specific to Memcheck">
-<title>Command-line flags specific to Memcheck</title>
+<sect1 id="mc-manual.options"
+ xreflabel="Memcheck Command-Line Options">
+<title>Memcheck Command-Line Options</title>
<!-- start of xi:include in the manpage -->
<variablelist id="mc.opts.list">
@@ -720,7 +720,7 @@
<para>Note that code that behaves in this way is in violation of
the the ISO C/C++ standards, and should be considered broken. If
- at all possible, such code should be fixed. This flag should be
+ at all possible, such code should be fixed. This option should be
used only as a last resort.</para>
</listitem>
</varlistentry>
@@ -742,7 +742,7 @@
accesses to blocks for some significant period of time after they
have been freed.</para>
- <para>This flag specifies the maximum total size, in bytes, of the
+ <para>This option specifies the maximum total size, in bytes, of the
blocks in the queue. The default value is ten million bytes.
Increasing this increases the total amount of memory used by
Memcheck but may detect invalid uses of freed
@@ -760,11 +760,11 @@
does not report them. The "small distance" is 256 bytes by
default. Note that GCC 2.96 is the default compiler on some ancient
Linux distributions (RedHat 7.X) and so you may need to use this
- flag. Do not use it if you do not have to, as it can cause real
+ option. Do not use it if you do not have to, as it can cause real
errors to be overlooked. A better alternative is to use a more
recent GCC in which this bug is fixed.</para>
- <para>You may also need to use this flag when working with
+ <para>You may also need to use this option when working with
GCC 3.X or 4.X on 32-bit PowerPC Linux. This is because
GCC generates code which occasionally accesses below the
stack pointer, particularly for floating-point to/from integer
@@ -796,7 +796,7 @@
by <computeroutput>calloc</computeroutput>, with the specified
byte. This can be useful when trying to shake out obscure
memory corruption problems. The allocated area is still
- regarded by Memcheck as undefined -- this flag only affects its
+ regarded by Memcheck as undefined -- this option only affects its
contents.
</para>
</listitem>
@@ -812,7 +812,7 @@
<computeroutput>delete</computeroutput>, etc, with the
specified byte value. This can be useful when trying to shake out
obscure memory corruption problems. The freed area is still
- regarded by Memcheck as not valid for access -- this flag only
+ regarded by Memcheck as not valid for access -- this option only
affects its contents.
</para>
</listitem>
@@ -1173,7 +1173,7 @@
<para>There is a hazy boundary case to do with multi-byte loads from
addresses which are partially valid and partially invalid. See
- details of the flag <option>--partial-loads-ok</option> for details.
+ details of the option <option>--partial-loads-ok</option> for details.
</para>
</listitem>
@@ -1343,11 +1343,12 @@
<title>Memory Pools: describing and working with custom allocators</title>
<para>Some programs use custom memory allocators, often for performance
-reasons. Left to itself, Memcheck is unable to "understand" the
-behaviour of custom allocation schemes and so may miss errors and
-leaks in your program. What this section describes is a way to give
-Memcheck enough of a description of your custom allocator that it can
-make at least some sense of what is happening.</para>
+reasons. Left to itself, Memcheck is unable to understand the
+behaviour of custom allocation schemes as well as it understands the
+standard allocators, and so may miss errors and leaks in your program. What
+this section describes is a way to give Memcheck enough of a description of
+your custom allocator that it can make at least some sense of what is
+happening.</para>
<para>There are many different sorts of custom allocator, so Memcheck
attempts to reason about them using a loose, abstract model. We
@@ -1433,12 +1434,12 @@
<listitem>
<para>
<varname>VALGRIND_CREATE_MEMPOOL(pool, rzB, is_zeroed)</varname>:
- This request registers the address "pool" as the anchor address
- for a memory pool. It also provides a size "rzB", specifying how
- large the redzones placed around chunks allocated from the pool
- should be. Finally, it provides an "is_zeroed" flag that specifies
- whether the pool's chunks are zeroed (more precisely: defined)
- when allocated.
+ This request registers the address <varname>pool</varname> as the anchor
+ address for a memory pool. It also provides a size
+ <varname>rzB</varname>, specifying how large the redzones placed around
+ chunks allocated from the pool should be. Finally, it provides an
+ <varname>is_zeroed</varname> argument that specifies whether the pool's
+ chunks are zeroed (more precisely: defined) when allocated.
</para>
<para>
Upon completion of this request, no chunks are associated with the
@@ -1459,44 +1460,47 @@
<listitem>
<para><varname>VALGRIND_MEMPOOL_ALLOC(pool, addr, size)</varname>:
- This request informs Memcheck that a "size"-byte chunk has been
- allocated at "addr", and associates the chunk with the specified
- "pool". If the pool was created with nonzero "rzB" redzones, Memcheck
- will mark the "rzB" bytes before and after the chunk as NOACCESS. If
- the pool was created with the "is_zeroed" flag set, Memcheck will mark
- the chunk as DEFINED, otherwise Memcheck will mark the chunk as
- UNDEFINED.
+ This request informs Memcheck that a <varname>size</varname>-byte chunk
+ has been allocated at <varname>addr</varname>, and associates the chunk with the
+ specified
+ <varname>pool</varname>. If the pool was created with nonzero
+ <varname>rzB</varname> redzones, Memcheck will mark the
+ <varname>rzB</varname> bytes before and after the chunk as NOACCESS. If
+ the pool was created with the <varname>is_zeroed</varname> argument set,
+ Memcheck will mark the chunk as DEFINED, otherwise Memcheck will mark
+ the chunk as UNDEFINED.
</para>
</listitem>
<listitem>
<para><varname>VALGRIND_MEMPOOL_FREE(pool, addr)</varname>:
- This request informs Memcheck that the chunk at "addr" should no
- longer be considered allocated. Memcheck will mark the chunk
- associated with "addr" as NOACCESS, and delete its record of the
- chunk's existence.
+ This request informs Memcheck that the chunk at <varname>addr</varname>
+ should no longer be considered allocated. Memcheck will mark the chunk
+ associated with <varname>addr</varname> as NOACCESS, and delete its
+ record of the chunk's existence.
</para>
</listitem>
<listitem>
<para><varname>VALGRIND_MEMPOOL_TRIM(pool, addr, size)</varname>:
- This request "trims" the chunks associated with "pool". The request
- only operates on chunks associated with "pool". Trimming is formally
- defined as:</para>
+ This request trims the chunks associated with <varname>pool</varname>.
+ The request only operates on chunks associated with
+ <varname>pool</varname>. Trimming is formally defined as:</para>
<itemizedlist>
<listitem>
- <para> All chunks entirely inside the range [addr,addr+size) are
- preserved.</para>
+ <para> All chunks entirely inside the range
+ <varname>addr..(addr+size-1)</varname> are preserved.</para>
</listitem>
<listitem>
- <para>All chunks entirely outside the range [addr,addr+size) are
- discarded, as though <varname>VALGRIND_MEMPOOL_FREE</varname>
- was called on them. </para>
+ <para>All chunks entirely outside the range
+ <varname>addr..(addr+size-1)</varname> are discarded, as though
+ <varname>VALGRIND_MEMPOOL_FREE</varname> was called on them. </para>
</listitem>
<listitem>
<para>All other chunks must intersect with the range
- [addr,addr+size); areas outside the intersection are marked as
- NOACCESS, as though they had been independently freed with
+ <varname>addr..(addr+size-1)</varname>; areas outside the
+ intersection are marked as NOACCESS, as though they had been
+ independently freed with
<varname>VALGRIND_MEMPOOL_FREE</varname>.</para>
</listitem>
</itemizedlist>
@@ -1508,9 +1512,9 @@
<listitem>
<para><varname>VALGRIND_MOVE_MEMPOOL(poolA, poolB)</varname>: This
request informs Memcheck that the pool previously anchored at
- address "poolA" has moved to anchor address "poolB". This is a
- rare request, typically only needed if you
- <function>realloc</function> the header of a mempool.</para>
+ address <varname>poolA</varname> has moved to anchor address
+ <varname>poolB</varname>. This is a rare request, typically only needed
+ if you <function>realloc</function> the header of a mempool.</para>
<para>No memory-status bits are altered by this request.</para>
</listitem>
@@ -1518,11 +1522,12 @@
<para>
<varname>VALGRIND_MEMPOOL_CHANGE(pool, addrA, addrB,
size)</varname>: This request informs Memcheck that the chunk
- previously allocated at address "addrA" within "pool" has been
- moved and/or resized, and should be changed to cover the region
- [addrB,addrB+size). This is a rare request, typically only needed
- if you <function>realloc</function> a superblock or wish to
- extend a chunk without changing its memory-status bits.
+ previously allocated at address <varname>addrA</varname> within
+ <varname>pool</varname> has been moved and/or resized, and should be
+ changed to cover the region <varname>addrB..(addrB+size-1)</varname>. This
+ is a rare request, typically only needed if you
+ <function>realloc</function> a superblock or wish to extend a chunk
+ without changing its memory-status bits.
</para>
<para>No memory-status bits are altered by this request.
</para>
@@ -1531,10 +1536,10 @@
<listitem>
<para><varname>VALGRIND_MEMPOOL_EXISTS(pool)</varname>:
This request informs the caller whether or not Memcheck is currently
- tracking a mempool at anchor address "pool". It evaluates to 1 when
- there is a mempool associated with that address, 0 otherwise. This is a
- rare request, only useful in circumstances when client code might have
- lost track of the set of active mempools.
+ tracking a mempool at anchor address <varname>pool</varname>. It
+ evaluates to 1 when there is a mempool associated with that address, 0
+ otherwise. This is a rare request, only useful in circumstances when
+ client code might have lost track of the set of active mempools.
</para>
</listitem>
@@ -1585,7 +1590,7 @@
the same <computeroutput>mpicc</computeroutput> you use to build the
MPI application you want to debug. By default, Valgrind tries
<computeroutput>mpicc</computeroutput>, but you can specify a
-different one by using the configure-time flag
+different one by using the configure-time option
<option>--with-mpicc</option>. Currently the
wrappers are only buildable with
<computeroutput>mpicc</computeroutput>s which are based on GNU
|
|
From: <sv...@va...> - 2009-08-10 01:15:42
|
Author: njn
Date: 2009-08-10 02:15:30 +0100 (Mon, 10 Aug 2009)
New Revision: 10758
Log:
Be consistent in the naming of sections describing command-line options.
Also, use "option" rather than "flag" where possible, for consistency.
Modified:
trunk/docs/xml/FAQ.xml
trunk/docs/xml/manual-core-adv.xml
trunk/docs/xml/manual-core.xml
trunk/docs/xml/manual-intro.xml
Modified: trunk/docs/xml/FAQ.xml
===================================================================
--- trunk/docs/xml/FAQ.xml 2009-08-10 00:42:43 UTC (rev 10757)
+++ trunk/docs/xml/FAQ.xml 2009-08-10 01:15:30 UTC (rev 10758)
@@ -132,7 +132,7 @@
older glibc versions causes this crash.</para>
<para>Workaround for 1.1.X and later versions of Valgrind: use the
- <option>--run-libc-freeres=no</option> flag. You may then get space
+ <option>--run-libc-freeres=no</option> option. You may then get space
leak reports for glibc allocations (please don't report these to
the glibc people, since they are not real leaks), but at least the
program runs.</para>
@@ -424,7 +424,7 @@
<para>If you are tracing large trees of processes, it can be less
disruptive to have the output sent over the network. Give Valgrind
- the flag <option>--log-socket=127.0.0.1:12345</option> (if you want
+ the option <option>--log-socket=127.0.0.1:12345</option> (if you want
logging output sent to port <literal>12345</literal> on
<literal>localhost</literal>). You can use the valgrind-listener
program to listen on that port:</para>
@@ -557,7 +557,7 @@
<answer id="a-undeferrors">
<para>Prior to version 3.4.0, the answer was "we don't know how to do it
without huge performance penalties". As of 3.4.0, try using the
- <option>--track-origins=yes</option> flag. It will run slower than
+ <option>--track-origins=yes</option> option. It will run slower than
usual, but will give you extra information about the origin of
uninitialised values.</para>
Modified: trunk/docs/xml/manual-core-adv.xml
===================================================================
--- trunk/docs/xml/manual-core-adv.xml 2009-08-10 00:42:43 UTC (rev 10757)
+++ trunk/docs/xml/manual-core-adv.xml 2009-08-10 01:15:30 UTC (rev 10758)
@@ -511,7 +511,7 @@
<para>Figuring out what's going on given the dynamic nature of wrapping
can be difficult. The
-<option>--trace-redir=yes</option> flag makes
+<option>--trace-redir=yes</option> option makes
this possible
by showing the complete state of the redirection subsystem after
every
@@ -550,7 +550,7 @@
time an active specification is used for the first time.</para>
<para>Hence for maximum debugging effectiveness you will need to use both
-flags.</para>
+options.</para>
<para>One final comment. The function-wrapping facility is closely
tied to Valgrind's ability to replace (redirect) specified
Modified: trunk/docs/xml/manual-core.xml
===================================================================
--- trunk/docs/xml/manual-core.xml 2009-08-10 00:42:43 UTC (rev 10757)
+++ trunk/docs/xml/manual-core.xml 2009-08-10 01:15:30 UTC (rev 10758)
@@ -7,10 +7,10 @@
<chapter id="manual-core" xreflabel="Valgrind's core">
<title>Using and understanding the Valgrind core</title>
-<para>This chapter describes the Valgrind core services, flags and
-behaviours. That means it is relevant regardless of what particular
-tool you are using. The information should be sufficient for you to
-make effective day-to-day use of Valgrind. Advanced topics related to
+<para>This chapter describes the Valgrind core services, command-line
+options and behaviours. That means it is relevant regardless of what
+particular tool you are using. The information should be sufficient for you
+to make effective day-to-day use of Valgrind. Advanced topics related to
the Valgrind core are described in <xref linkend="manual-core-adv"/>.
</para>
@@ -41,7 +41,7 @@
valgrind --tool=memcheck ls -l]]></programlisting>
<para>However, Memcheck is the default, so if you want to use it you can
-omit the <option>--tool</option> flag.</para>
+omit the <option>--tool</option> option.</para>
<para>Regardless of which tool is in use, Valgrind takes control of your
program before it starts. Debugging information is read from the
@@ -94,17 +94,17 @@
<para>First off, consider whether it might be beneficial to recompile
your application and supporting libraries with debugging info enabled
-(the <option>-g</option> flag). Without debugging info, the best
+(the <option>-g</option> option). Without debugging info, the best
Valgrind tools will be able to do is guess which function a particular
piece of code belongs to, which makes both error messages and profiling
output nearly useless. With <option>-g</option>, you'll get
messages which point directly to the relevant source code lines.</para>
-<para>Another flag you might like to consider, if you are working with
+<para>Another option you might like to consider, if you are working with
C++, is <option>-fno-inline</option>. That makes it easier to see the
function-call chain, which can help reduce confusion when navigating
around large C++ apps. For example, debugging
-OpenOffice.org with Memcheck is a bit easier when using this flag. You
+OpenOffice.org with Memcheck is a bit easier when using this option. You
don't have to do this, but doing so helps Valgrind produce more accurate
and less confusing error reports. Chances are you're set up like this
already, if you intended to debug your program with GNU GDB, or some
@@ -145,7 +145,7 @@
<filename>/bin/sh</filename>,
<filename>/usr/bin/perl</filename>, or whatever interpreter
you're using. This may not be what you want and can be confusing. You
-can force the issue by giving the flag
+can force the issue by giving the option
<option>--trace-children=yes</option>, but confusion is still
likely.</para>
@@ -171,7 +171,7 @@
<para>By default, Valgrind tools write only essential messages to the
commentary, so as to avoid flooding you with information of secondary
importance. If you want more information about what is happening,
-re-run, passing the <option>-v</option> flag to Valgrind. A second
+re-run, passing the <option>-v</option> option to Valgrind. A second
<option>-v</option> gives yet more detail.
</para>
@@ -235,7 +235,7 @@
connections in round brackets.</para>
<para><computeroutput>valgrind-listener</computeroutput> accepts two
- command-line flags:</para>
+ command-line options:</para>
<itemizedlist>
<listitem>
<para><option>-e</option> or <option>--exit-at-zero</option>:
@@ -335,8 +335,8 @@
if necessary.</para>
<para>To avoid this cutoff you can use the
-<option>--error-limit=no</option> flag. Then Valgrind will always show
-errors, regardless of how many there are. Use this flag carefully,
+<option>--error-limit=no</option> option. Then Valgrind will always show
+errors, regardless of how many there are. Use this option carefully,
since it may have a bad effect on performance.</para>
</sect1>
@@ -361,8 +361,8 @@
them.</para>
<formalpara><title>Note:</title> <para>By far the easiest way to add
-suppressions is to use the <option>--gen-suppressions=yes</option> flag
-described in <xref linkend="manual-core.flags"/>. This generates
+suppressions is to use the <option>--gen-suppressions=yes</option> option
+described in <xref linkend="manual-core.options"/>. This generates
suppressions automatically. For best results,
though, you may want to edit the output
of <option>--gen-suppressions=yes</option> by hand, in which
@@ -376,7 +376,7 @@
suppression mechanism is designed to allow precise yet flexible
specification of errors to suppress.</para>
-<para>If you use the <option>-v</option> flag, at the end of execution,
+<para>If you use the <option>-v</option> option, at the end of execution,
Valgrind prints out one line for each used suppression, giving its name
and the number of times it got used. Here's the suppressions used by a
run of <computeroutput>valgrind --tool=memcheck ls -l</computeroutput>:</para>
@@ -550,19 +550,19 @@
</sect1>
-<sect1 id="manual-core.flags"
- xreflabel="Command-line flags for the Valgrind core">
-<title>Command-line flags for the Valgrind core</title>
+<sect1 id="manual-core.options"
+ xreflabel="Core Command-line Options">
+<title>Core Command-line Options</title>
-<para>As mentioned above, Valgrind's core accepts a common set of flags.
-The tools also accept tool-specific flags, which are documented
+<para>As mentioned above, Valgrind's core accepts a common set of options.
+The tools also accept tool-specific options, which are documented
separately for each tool.</para>
<para>Valgrind's default settings succeed in giving reasonable behaviour
in most cases. We group the available options by rough categories.</para>
-<sect2 id="manual-core.toolopts" xreflabel="Tool-selection option">
-<title>Tool-selection option</title>
+<sect2 id="manual-core.toolopts" xreflabel="Tool-selection Option">
+<title>Tool-selection Option</title>
<para>The single most important option.</para>
@@ -637,7 +637,7 @@
of your program, such as: the shared objects loaded, the
suppressions used, the progress of the instrumentation and
execution engines, and warnings about unusual behaviour. Repeating
- the flag increases the verbosity level.</para>
+ the option increases the verbosity level.</para>
</listitem>
</varlistentry>
@@ -671,7 +671,7 @@
a <varname>fork</varname> call. This can make the output less
confusing (although more misleading) when dealing with processes
that create children. It is particularly useful in conjunction
- with <varname>--trace-children=</varname>. Use of this flag is also
+ with <varname>--trace-children=</varname>. Use of this option is also
strongly recommended if you are requesting XML output
(<varname>--xml=yes</varname>), since otherwise the XML from child and
parent may become mixed up, which usually makes it useless.
@@ -780,7 +780,7 @@
<sect2 id="manual-core.erropts" xreflabel="Error-related Options">
-<title>Error-related options</title>
+<title>Error-related Options</title>
<!-- start of xi:include in the manpage -->
<para id="error-related.opts.para">These options are used by all tools
@@ -815,7 +815,7 @@
<computeroutput>docs/internals/xml-output-protocol4.txt</computeroutput>
in the source tree for Valgrind 3.5.0 or later.</para>
- <para>The recommended flags for a GUI to pass, when requesting
+ <para>The recommended options for a GUI to pass, when requesting
XML output, are: <option>--xml=yes</option> to enable XML output,
<option>--xml-file</option> to send the XML output to a (presumably
GUI-selected) file, <option>--log-file</option> to send the plain
@@ -1079,7 +1079,7 @@
debugged.</para>
<para>Since <computeroutput><command></computeroutput> is likely
- to contain spaces, you will need to put this entire flag in
+ to contain spaces, you will need to put this entire option in
quotes to ensure it is correctly handled by the shell.</para>
</listitem>
</varlistentry>
@@ -1104,7 +1104,7 @@
<option><![CDATA[--dsymutil=no|yes [no] ]]></option>
</term>
<listitem>
- <para>This flag is only relevant when running Valgrind on
+ <para>This option is only relevant when running Valgrind on
Mac OS X.</para>
<para>Mac OS X uses a deferred debug information (debuginfo)
@@ -1184,7 +1184,7 @@
option allows you to change the threshold to a different
value.</para>
- <para>You should only consider use of this flag if Valgrind's
+ <para>You should only consider use of this option if Valgrind's
debug output directs you to do so. In that case it will tell you
the new threshold you should specify.</para>
@@ -1194,7 +1194,7 @@
support large numbers of threads each with a small stack, and also
because the error checking performed by Memcheck is more effective
for heap-allocated data than for stack-allocated data. If you
- have to use this flag, you may wish to consider rewriting your
+ have to use this option, you may wish to consider rewriting your
code to allocate on the heap rather than on the stack.</para>
</listitem>
</varlistentry>
@@ -1337,7 +1337,7 @@
and ppc64/Linux, Valgrind always provides complete, transparent
support for self-modifying code. It is only on platforms such as
x86/Linux, AMD64/Linux and x86/Darwin that you need to use this
- flag.</para>
+ option.</para>
</listitem>
</varlistentry>
@@ -1385,7 +1385,7 @@
<option><![CDATA[--run-libc-freeres=<yes|no> [default: yes] ]]></option>
</term>
<listitem>
- <para>This flag is only relevant when running Valgrind on Linux.</para>
+ <para>This option is only relevant when running Valgrind on Linux.</para>
<para>The GNU C library (<function>libc.so</function>), which is
used by all programs, may allocate memory for its own uses.
@@ -1405,7 +1405,7 @@
<para>Unfortunately, in some very old versions of glibc,
<function>__libc_freeres</function> is sufficiently buggy to cause
segmentation faults. This was particularly noticeable on Red Hat
- 7.1. So this flag is provided in order to inhibit the run of
+ 7.1. So this option is provided in order to inhibit the run of
<function>__libc_freeres</function>. If your program seems to run
fine on Valgrind, but segfaults at exit, you may find that
<option>--run-libc-freeres=no</option> fixes that, although at the
@@ -1480,8 +1480,8 @@
</sect2>
-<sect2 id="manual-core.debugopts" xreflabel="Debugging Valgrind Options">
-<title>Debugging Valgrind Options</title>
+<sect2 id="manual-core.debugopts" xreflabel="Debugging Options">
+<title>Debugging Options</title>
<!-- start of xi:include in the manpage -->
<para id="debug.opts.para">There are also some options for debugging
@@ -1493,8 +1493,8 @@
</sect2>
-<sect2 id="manual-core.defopts" xreflabel="Setting default options">
-<title>Setting default Options</title>
+<sect2 id="manual-core.defopts" xreflabel="Setting Default Options">
+<title>Setting Default Options</title>
<para>Note that Valgrind also reads options from three places:</para>
@@ -1639,7 +1639,7 @@
<para>This builds Valgrind with some special magic hacks which make
it possible to run it on a standard build of Valgrind (what the
developers call "self-hosting"). Ordinarily you should not use
- this flag as various kinds of safety checks are disabled.
+ this option as various kinds of safety checks are disabled.
</para>
</listitem>
@@ -1659,7 +1659,7 @@
platforms (amd64-linux, ppc64-linux), Valgrind is by default built
in such a way that both 32-bit and 64-bit executables can be run.
Sometimes this cleverness is a problem for a variety of reasons.
- These two flags allow for single-target builds in this situation.
+ These two options allow for single-target builds in this situation.
If you issue both, the configure script will complain. Note they
are ignored on 32-bit-only platforms (x86-linux, ppc32-linux).
</para>
@@ -1784,7 +1784,7 @@
code has changed, and work correctly. This is necessary to handle
the trampolines GCC uses to implemented nested functions. If you
regenerate code somewhere other than the stack, you will need to use
- the <option>--smc-check=all</option> flag, and Valgrind will run more
+ the <option>--smc-check=all</option> option, and Valgrind will run more
slowly than normal. Or you can add client requests that tell Valgrind
when your program has overwritten code.</para>
</listitem>
Modified: trunk/docs/xml/manual-intro.xml
===================================================================
--- trunk/docs/xml/manual-intro.xml 2009-08-10 00:42:43 UTC (rev 10757)
+++ trunk/docs/xml/manual-intro.xml 2009-08-10 01:15:30 UTC (rev 10758)
@@ -112,7 +112,7 @@
<title>How to navigate this manual</title>
<para>This manual's structure reflects the structure of Valgrind itself.
-First, we describe the Valgrind core, how to use it, and the flags
+First, we describe the Valgrind core, how to use it, and the options
it supports. Then, each tool has its own chapter in this manual. You
only need to read the documentation for the core and for the tool(s) you
actually use, although you may find it helpful to be at least a little
@@ -120,10 +120,10 @@
want to run the Memcheck tool and you might find the <xref
linkend="quick-start"/> useful.</para>
-<para>Be aware that the core understands some command line flags, and
-the tools have their own flags which they know about. This means
-there is no central place describing all the flags that are
-accepted -- you have to read the flags documentation both for
+<para>Be aware that the core understands some command line options, and
+the tools have their own options which they know about. This means
+there is no central place describing all the options that are
+accepted -- you have to read the options documentation both for
<xref linkend="manual-core"/> and for the tool you want to use.</para>
|
|
From: <sv...@va...> - 2009-08-10 00:48:43
|
Author: njn
Date: 2009-08-10 01:42:43 +0100 (Mon, 10 Aug 2009)
New Revision: 10757
Log:
Remove some cross-references that are broken in the man pages because they
only include a subset of the User Manual.
Modified:
trunk/callgrind/docs/cl-manual.xml
trunk/docs/xml/manual-core.xml
Modified: trunk/callgrind/docs/cl-manual.xml
===================================================================
--- trunk/callgrind/docs/cl-manual.xml 2009-08-09 23:27:00 UTC (rev 10756)
+++ trunk/callgrind/docs/cl-manual.xml 2009-08-10 00:42:43 UTC (rev 10757)
@@ -722,7 +722,12 @@
implicitly sets
<option>--collect-state=no</option>.</para>
<para>Collection state can be toggled also by inserting the client request
- <computeroutput><xref linkend="cr.toggle-collect"/>;</computeroutput>
+ <computeroutput>
+ <!-- commented out because it causes broken links in the man page
+ <xref linkend="cr.toggle-collect"/>;
+ -->
+ CALLGRIND_TOGGLE_COLLECT
+ ;</computeroutput>
at the needed code positions.</para>
</listitem>
</varlistentry>
Modified: trunk/docs/xml/manual-core.xml
===================================================================
--- trunk/docs/xml/manual-core.xml 2009-08-09 23:27:00 UTC (rev 10756)
+++ trunk/docs/xml/manual-core.xml 2009-08-10 00:42:43 UTC (rev 10757)
@@ -1010,9 +1010,12 @@
wildcards to function names, and by using frame-level wildcards.
The wildcarding facilities are powerful yet flexible, and with a
bit of careful editing, you may be able to suppress a whole
- family of related errors with only a few suppressions. For
- details on how to do this, see
- <xref linkend="manual-core.suppress"/>.</para>
+ family of related errors with only a few suppressions.
+ <!-- commented out because it causes broken links in the man page
+ For details on how to do this, see
+ <xref linkend="manual-core.suppress"/>.
+ -->
+ </para>
<para>Sometimes two different errors
are suppressed by the same suppression, in which case Valgrind
@@ -1320,8 +1323,12 @@
code gets put on the stack for most programs. The
<function>VALGRIND_DISCARD_TRANSLATIONS</function> client request is
an alternative to <option>--smc-check=all</option> that requires more
- effort but is much faster; see <xref
- linkend="manual-core-adv.clientreq"/> for more details.</para>
+ effort but is much faster.
+ <!-- commented out because it causes broken links in the man page
+ ; see <xref
+ linkend="manual-core-adv.clientreq"/> for more details.
+ -->
+ </para>
<para>Some architectures (including ppc32 and ppc64) require
programs which create code at runtime to flush the instruction
|